<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text><span class="style20">┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.06.0/1 Automated Security Measures 6.0/2 Warning of Threats to Security 6.0/3 Protection from Computer Failure 6.0/4 Protection from Interference by Other Users 6.0/5 Protection from Interrupts 6.0/6 Segregating Real from Simulated Data 6.0/7 Consistent Procedures 6.0/8 Appropriate Ease or Difficulty of User Actions 6.0/9 Control by Explicit User Action 6.0/10 User Review and Editing of Entries 6.0/11 Disabling Unneeded Controls 6.0/12 Protecting Physical Controls 6.0/13 Safe Defaults 6.0/14 Safe Response to Random Inputs 6.0/15 Explicit Action to Select Destructive Modes 6.0/16 Feedback for Mode Selection 6.0/17 Warning Users of Potential Data Loss 6.0/18 User Confirmation of Destructive Actions 6.0/19 Distinctive CONFIRM Action 6.0/20 Separate CONFIRM Action 6.0/21 Reversible Control Actions (UNDO) ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.16.1/1 Easy LOG-ON 6.1/2 Prompting LOG-ON 6.1/3 User Choice of Passwords 6.1/4 Changing Passwords 6.1/5 Private Entry of Passwords 6.1/6 Limiting Unsuccessful LOG-ON Attempts 6.1/7 Auxiliary Tests to Authenticate User Identity 6.1/8 Continuous Recognition of User Identity ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.26.2/1 Single Authorization for Data Access 6.2/2 Displayed Security Classification 6.2/3 Protecting Displayed Data 6.2/4 Indicating Read-Only Displays 6.2/5 Protecting Display Formats 6.2/6 Display Suppression for Security 6.2/7 Protecting Printed Data 6.2/8 Automatic Records of Data Access 6.2/9 Encryption 6.2/10 Ensuring Reversible Encryption ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.36.3/1 Single Authorization for Data Entry/Change 6.3/2 Protection from Data Change 6.3/3 Data Entry/Change Transaction Records 6.3/4 Simple Procedures 6.3/5 Explicit User Actions6.3/6 Single Entry of Related Data 6.3/7 Data Entry Independent of Cursor Placement 6.3/8 Editing Data Before Entry 6.3/9 Immediate Error Correction 6.3/10 Editing Entries After Error Detection 6.3/11 Explicit Entry of Corrections 6.3/12 Flexible BACKUP for Error Correction 6.3/13 Data Verification by User Review 6.3/14 Automatic Data Generation 6.3/15 Displaying Default Values 6.3/16 Displaying Data to be Changed 6.3/17 Validating Data Changes 6.3/18 Cross Validation of Related Data 6.3/19 User Confirmation of Destructive Actions 6.3/20 Distinctive File Names 6.3/21 Segregating Real from Simulated Data 6.3/22 Preventing Data Loss at LOG-OFF ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.46.4/1 Automatic Protection of Transmitted Data 6.4/2 User Review of Data Before Transmission 6.4/3 Encrypting Messages 6.4/4 Saving Transmitted Data Until Receipt is Confirmed 6.4/5 Nondisruptive Notification of Messages Received 6.4/6 Authenticating Message Sources 6.4/7 Printing Messages ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗6.56.5/1 Flexible Design for Data Protection 6.5/2 Protection from Design Change </span><span class="style1"></span></text>
</content>
<content>
<layer>card</layer>
<id>26</id>
<text>6.0 General 6.1 User Identification 6.2 Data Access 6.3 Data Entry/Change 6.4 Data Transmission 6.5 Design Change </text>
</content>
<name>Data Protection</name>
<script></script>
</card>
card_8661.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text><span class="style20">┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.05.0/1 Functional Integration 5.0/2 Functional Wording 5.0/3 Consistent Procedures 5.0/4 Minimal Memory Load on User 5.0/5 Minimal User Actions 5.0/6 Control by Explicit User Action 5.0/7 Flexible User Control 5.0/8 Interrupt 5.0/9 Flexible Message Filing 5.0/10 Message Highlighting ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.15.1/1 Message Composition Compatible with Data Entry 5.1/2 User-Designed Message Formats5.1/3 Unformatted Text 5.1/4 Stored Message Forms 5.1/5 Automatic Message Formatting 5.1/6 Automatic Text Formatting 5.1/7 Data Forms 5.1/8 Tables and Graphics 5.1/9 Flexible Data Specification 5.1/10 Incorporate Existing Files 5.1/11 Incorporate Other Messages 5.1/12 Variable Message Length 5.1/13 Saving Draft Messages ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.25.2/1 Destination Selection 5.2/2 Standard Address Header 5.2/3 Prompting Address Entry 5.2/4 Address Directory 5.2/5 Aids for Directory Search 5.2/6 Extracting Directory Addresses 5.2/7 User-Assigned Nicknames for Addressing 5.2/8 System Distribution Lists 5.2/9 Access to Distribution List Information 5.2/10 Informal Distribution Lists 5.2/11 Lists Within Lists 5.2/12 Modifying Distribution Lists 5.2/13 Automatic Expansion of Partial Addresses 5.2/14 Automatic Address Checking 5.2/15 Addressing Replies to Messages Received 5.2/16 Editing Address Headers 5.2/17 Single Occurrence of Address 5.2/18 Serial Distribution 5.2/19 Redistributing Received Messages ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.35.3/1 User-Initiated Transmission 5.3/2 User Review Before Transmission 5.3/3 Optional Message Display 5.3/4 Computer-Initiated Transmission 5.3/5 Information About Communication Status 5.3/6 Sender Identification 5.3/7 Assignment of Priority 5.3/8 Automatic Queuing for Transmission 5.3/9 Deferring Message Transmission 5.3/10 Transmission at Specified Date/Time 5.3/11 Return Receipt 5.3/12 Cancel Transmission 5.3/13 Printing Messages ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.45.4/1 Automatic Protection of Transmitted Data 5.4/2 Automatic Feedback 5.4/3 User Specification of Feedback 5.4/4 Send Single Copy 5.4/5 Queuing Failed Transmissions 5.4/6 Saving Undelivered Messages 5.4/7 Notification of Transmission Failure 5.4/8 Message Recall 5.4/9 Automatic Record Keeping ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.55.5/1 Specifying Sources 5.5/2 Specifying Device Destination 5.5/3 Queuing Messages Received 5.5/4 Message Notification at LOG-ON 5.5/5 Nondisruptive Notification of Arriving Messages 5.5/6 Indicating Priority of Received Messages 5.5/7 Filters for Message Notification 5.5/8 Warning of Incompatible Format 5.5/9 Information about Queued Messages 5.5/10 Indicate Message Size 5.5/11 Specifying Format for Message Listings 5.5/12 User Review of Messages in Queue 5.5/13 Filters for Ordering Message Review 5.5/14 Message Review Compatible with Data Display 5.5/15 Labeling Received Messages5.5/16 Annotating Received Messages 5.5/17 Filters for Message Filing 5.5/18 Discarding Messages ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗5.65.6/1 Flexible Design for Data Transmission </span><span class="style1"></span></text>
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text><span class="style20">┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.04.0/1 Standard Procedures 4.0/2 Explicit User Actions 4.0/3 Separate LOG-ON Procedure 4.0/4 Display of Guidance Information 4.0/5 Only Necessary Information Displayed4.0/6 Consistent Display Format 4.0/7 Consistent Format for User Guidance 4.0/8 Distinctive Format for User Guidance 4.0/9 Distinctive Cursor 4.0/10 Clear Control Labels 4.0/11 Clear Data Labels 4.0/12 Highlighting Critical User Guidance 4.0/13 Consistent Coding Conventions 4.0/14 Familiar Coding Conventions 4.0/15 Consistent Wording 4.0/16 Familiar Wording 4.0/17 Task-Oriented Wording 4.0/18 Wording Consistent with Control Entry 4.0/19 Speaking Directly to Users 4.0/20 Affirmative Statements 4.0/21 Active Voice 4.0/22 Temporal Sequence 4.0/23 Consistent Grammatical Structure 4.0/24 Flexible User Guidance 4.0/25 Easy Ways to Get Guidance 4.0/26 Speech Output 4.0/27 Limited Number of Spoken Messages 4.0/28 Simple Spoken Messages 4.0/29 Distinctive Spoken Warnings ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.14.1/1 Indicating Status 4.1/2 Automatic LOG-ON Display 4.1/3 LOG-ON Delay 4.1/4 Keyboard Lock 4.1/5 Operational Mode 4.1/6 Other Users 4.1/7 System Load 4.1/8 External Systems 4.1/9 Date and Time Signals 4.1/10 Alarm Settings ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.24.2/1 Consistent Feedback 4.2/2 Fast Response 4.2/3 Feedback for Control Entries 4.2/4 Indicating Completion of Processing 4.2/5 Feedback for Print Requests 4.2/6 Display Identification 4.2/7 Identifying Multipage Displays 4.2/8 Indicating Operational Mode 4.2/9 Indicating Option Selection 4.2/10 Indicating Item Selection 4.2/11 Feedback for User Interrupt ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.34.3/1 Informative Error Messages 4.3/2 Specific Error Messages 4.3/3 Task-Oriented Error Messages 4.3/4 Advisory Error Messages 4.3/5 Brief Error Messages 4.3/6 Neutral Wording for Error Messages 4.3/7 Multilevel Error Messages 4.3/8 Multiple Error Messages 4.3/9 Indicating Repeated Errors 4.3/10 Non-Disruptive Error Messages 4.3/11 Appropriate Response Time for Error Messages 4.3/12 Documenting Error Messages 4.3/13 Cursor Placement Following Error 4.3/14 Displaying Erroneous Entries 4.3/15 User Editing of Entry Errors 4.3/16 Removing Error Messages 4.3/17 Cautionary Messages 4.3/18 User Confirmation of Destructive Entries 4.3/19 Alarm Coding ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.44.4/1 Guidance Information Always Available 4.4/2 General List of Control Options 4.4/3 Logical Menu Structure 4.4/4 Hierarchic Menus 4.4/5 Guidance for Sequence Control 4.4/6 Transaction-Specific Option Display 4.4/7 Prompting Entries 4.4/8 Standard Display Location for Prompting 4.4/9 Consistent Format for Prompts 4.4/10 Standard Symbol for Prompting Entry 4.4/11 Concise Wording of Prompts 4.4/12 User-Requested Prompts 4.4/13 Displayed Context 4.4/14 Maintaining Context for Data Entry 4.4/15 Cues for Prompting Data Entry 4.4/16 Consistent Cursor Positioning 4.4/17 On-Line System Guidance 4.4/18 Index of Data 4.4/19 Index of Commands 4.4/20 Dictionary of Abbreviations 4.4/21 Definition of Display Codes 4.4/22 Record of Past Transactions 4.4/23 HELP 4.4/24 Standard Action to Request HELP 4.4/25 Task-Oriented HELP 4.4/26 Clarifying HELP Requests 4.4/27 Synonyms for Standard Terminology 4.4/28 Multilevel HELP 4.4/29 Browsing HELP 4.4/30 On-Line Training 4.4/31 Flexible Training 4.4/32 Adaptive Training ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.54.5/1 User Performance Measurement 4.5/2 Notifying Users 4.5/3 Transaction Records 4.5/4 Data Access Records 4.5/5 Records of Program Use 4.5/6 Error Records 4.5/7 HELP Records ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗4.64.6/1 Flexible Design for User Guidance 4.6/2 Notifying Users of Design Changes </span><span class="style1"></span></text>
</content>
<content>
<layer>card</layer>
<id>26</id>
<text>4.0 General 4.1 Status Information 4.2 Routine Feedback 4.3 Error Feedback 4.4 Job Aids 4.5 User Records 4.6 Design Change </text>
</content>
<name>User Guidance</name>
<script></script>
</card>
card_6983.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text><span class="style20">┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.03.0/1 Flexible Sequence Control 3.0/2 Minimal User Actions 3.0/3 Control Matched to User Skill 3.0/4 User Initiative in Sequence Control 3.0/5 Control by Explicit User Action 3.0/6 Consistent User Actions 3.0/7 Logical Transaction Sequences 3.0/8 Distinctive Display of Control Information 3.0/9 Displayed Context 3.0/10 Consistent Terminology for Sequence Control 3.0/11 Congruent Names for Control Functions 3.0/12 Upper and Lower Case Equivalent 3.0/13 Wording Consistent with User Guidance 3.0/14 Feedback for Control Entries 3.0/15 Indicating Completion of Processing 3.0/16 Compatibility with User Expectations 3.0/17 User-Paced Sequence Control 3.0/18 Appropriate Computer Response Time 3.0/19 Control Availability 3.0/20 Indicating Control Lockout 3.0/21 Interrupt to End Control Lockout 3.0/22 Control by Simultaneous Users ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.13.1/1 Dialogue Matched to Task and User 3.1/2 Appropriate Computer Response Time ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.13.1.1/1 Question-and-Answer Dialogue 3.1.1/2 Questions Displayed Singly 3.1.1/3 Recapitulating Prior Answers 3.1.1/4 Sequence Compatible with Source Documents ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.23.1.2/1 Form Filling for Data Entry 3.1.2/2 Form Filling for Control Entry 3.1.2/3 Defaults for Control Entry 3.1.2/4 Consistent Format for Control Forms ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.33.1.3/1 Menu Selection 3.1.3/2 Single Selection Per Menu 3.1.3/3 Single-Column List Format 3.1.3/4 Menu Selection by Pointing 3.1.3/5 Large Pointing Area for Option Selection 3.1.3/6 Dual Activation for Pointing 3.1.3/7 Menu Selection by Keyed Entry 3.1.3/8 Standard Area for Code Entry 3.1.3/9 Feedback for Menu Selection 3.1.3/10 Explanatory Title for Menu 3.1.3/11 Menu Options Worded as Commands 3.1.3/12 Option Wording Consistent with Command Language 3.1.3/13 Letter Codes for Menu Selection 3.1.3/14 Consistent Coding of Menu Options 3.1.3/15 Standard Symbol for Prompting Entry 3.1.3/16 Explicit Option Display 3.1.3/17 Complete Display of Menu Options 3.1.3/18 Menu Options Dependent on Context 3.1.3/19 Consistent Display of Menu Options 3.1.3/20 Menus Distinct from Other Displayed Information 3.1.3/21 Logical Ordering of Menu Options 3.1.3/22 Logical Grouping of Menu Options 3.1.3/23 Logical Ordering of Grouped Options 3.1.3/24 Labeling Grouped Options 3.1.3/25 Hierarchic Menus for Sequential Selection 3.1.3/26 General Menu 3.1.3/27 Minimal Steps in Sequential Menu Selection 3.1.3/28 Easy Selection of Important Options 3.1.3/29 Automatic Cursor Placement 3.1.3/30 Indicating Current Position in Menu Structure 3.1.3/31 Control Options Distinct from Menu Branching 3.1.3/32 Consistent Design of Hierarchic Menus 3.1.3/33 Return to Higher-Level Menus 3.1.3/34 Return to General Menu 3.1.3/35 By-Passing Menu Selection with Command Entry 3.1.3/36 Stacking Menu Selections ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.43.1.4/1 Function Keys for Critical Control Entries 3.1.4/2 Function Keys for Frequent Control Entries 3.1.4/3 Function Keys for Interim Control Entries 3.1.4/4 Distinctive Labeling of Function Keys 3.1.4/5 Labeling Multifunction Keys 3.1.4/6 Single Keying for Frequent Functions 3.1.4/7 Logical Pairing of Double-Keyed Functions 3.1.4/8 Consistent Logic for Double Keying 3.1.4/9 Single Activation of Function Keys 3.1.4/10 Feedback for Function Key Activation 3.1.4/11 Indicating Active Function Keys 3.1.4/12 Disabling Unneeded Function Keys 3.1.4/13 Single Key for Continuous Functions 3.1.4/14 Consistent Assignment of Function Keys 3.1.4/15 Consistent Functions in Different Operational Modes 3.1.4/16 Easy Return to Base-Level Functions 3.1.4/17 Distinctive Location 3.1.4/18 Layout Compatible with Use ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.53.1.5/1 Command Language 3.1.5/2 Standard Display Area for Command Entry 3.1.5/3 Functional Wording 3.1.5/4 Layered Command Language 3.1.5/5 Meaningful Command Names 3.1.5/6 Familiar Wording 3.1.5/7 Consistent Wording of Commands 3.1.5/8 Distinctive Meaning for Commands 3.1.5/9 Distinctive Spelling for Commands 3.1.5/10 User-Assigned Command Names 3.1.5/11 User-Requested Prompts 3.1.5/12 General List of Commands 3.1.5/13 Command Stacking 3.1.5/14 User Definition of Macro Commands 3.1.5/15 Minimal Punctuation 3.1.5/16 Standard Delimiter 3.1.5/17 Ignoring Blanks in Command Entry 3.1.5/18 Abbreviation of Commands 3.1.5/19 Standard Techniques for Command Editing 3.1.5/20 Interpreting Misspelled Commands 3.1.5/21 Recognizing Command Synonyms 3.1.5/22 Recognizing Alternative Syntax 3.1.5/23 Correcting Command Entry Errors 3.1.5/24 Replacing Erroneous Commands 3.1.5/25 Reviewing Destructive Commands ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.63.1.6/1 Query Language 3.1.6/2 Natural Organization of Data 3.1.6/3 Coherent Representation of Data Organization 3.1.6/4 Task-Oriented Wording 3.1.6/5 Flexible Query Formulation 3.1.6/6 Minimal Need for Quantifiers 3.1.6/7 Logic to Link Queries 3.1.6/8 Linking Sequential Queries 3.1.6/9 Confirming Large-Scale Retrieval ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.73.1.7/1 Constrained Natural Language ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.1.83.1.8/1 Control of Graphic Data 3.1.8/2 Graphic Control Aids for Casual Users 3.1.8/3 Iconic Menus 3.1.8/4 Supplementary Verbal Labels 3.1.8/5 Direct Manipulation 3.1.8/6 Graphic Display of Control Context 3.1.8/7 Graphic Display of Control Prompting ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.23.2/1 User Control in Transaction Selection 3.2/2 General List of Control Options 3.2/3 Organization and Labeling of Listed Options 3.2/4 Indicating Appropriate Control Options 3.2/5 Prompting Control Entries 3.2/6 Cursor Placement for Pointing at Options 3.2/7 Cursor Placement for Keyed Entry of Options 3.2/8 Displaying Option Codes 3.2/9 Task-Oriented Wording for Options 3.2/10 Only Available Options Offered 3.2/11 Indicating Control Defaults 3.2/12 Consistent CONTINUE Option 3.2/13 Stacked Control Entries 3.2/14 Consistent Order in Entry Stacking 3.2/15 Abbreviation in Entry Stacking 3.2/16 Minimal Punctuation of Stacked Entries 3.2/17 Standard Delimiter in Entry Stacking 3.2/18 User Definition of Macro Commands 3.2/19 User-Specified Transaction Timing ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.33.3/1 User Interruption of Transactions 3.3/2 Distinctive Interrupt Options 3.3/3 CANCEL Option 3.3/4 BACKUP Option 3.3/5 REVIEW Option 3.3/6 RESTART Option 3.3/7 END Option 3.3/8 PAUSE and CONTINUE Options 3.3/9 Indicating PAUSE Status 3.3/10 SUSPEND Option 3.3/11 Indicating SUSPEND Status ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.43.4/1 Defining Context for Users 3.4/2 Context Established by Prior Entries 3.4/3 Record of Prior Entries 3.4/4 Display of Operational Mode 3.4/5 Display of Control Parameters 3.4/6 Highlighting Selected Data 3.4/7 Consistent Display of Context Information ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.53.5/1 Appropriate Response to All Entries 3.5/2 Command Editing 3.5/3 Prompting Command Correction 3.5/4 Errors in Stacked Commands 3.5/5 Partial Execution of Stacked Commands 3.5/6 Explicit Entry of Corrections 3.5/7 User Confirmation of Destructive Entries 3.5/8 User Warned of Potential Data Loss 3.5/9 Distinctive CONFIRM Action 3.5/10 UNDO to Reverse Control Actions 3.5/11 Preventing Data Loss at LOG-OFF 3.5/12 Immediate Data Correction 3.5/13 Flexible BACKUP for Error Correction ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.63.6/1 Alarm Definition by Users 3.6/2 Distinctive and Consistent Alarms 3.6/3 Alarm Acknowledgment 3.6/4 Alarm Reset 3.6/5 Special Acknowledgment of Critical Alarms ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗3.73.7/1 Flexible Design for Sequence Control </span><span class="style1"></span></text>
<text>3.1 Dialogue Type - General3.1.1 Dialogue Type - Question and Answer 3.1.2 Dialogue Type - Form Filling 3.1.3 Dialogue Type - Menu Selection 3.1.4 Dialogue Type - Function Keys 3.1.5 Dialogue Type - Command Language 3.1.6 Dialogue Type - Query Language 3.1.7 Dialogue Type - Natural Language 3.1.8 Dialogue Type - Graphic Interaction </text>
</content>
<name>Sequence Control</name>
<script></script>
</card>
card_7919.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<part>
<id>29</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <true /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>64</left>
<top>149</top>
<right>240</right>
<bottom>203</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Avant Garde</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>Display</name>
<script>on mouseUpsectionend mouseUp</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text><span class="style20">┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.02.0/1 Necessary Data Displayed 2.0/2 Only Necessary Data Displayed 2.0/3 Data Displayed in Usable Form 2.0/4 Data Display Consistent with User Conventions 2.0/5 Establishing Display Standards 2.0/6 Consistent Display Format 2.0/7 Display Consistent with Entry Requirements 2.0/8 User Control of Data Display 2.0/9 User Changes to Displayed Data 2.0/10 Protection of Displayed Data 2.0/11 Context for Displayed Data 2.0/12 Familiar Wording 2.0/13 Consistent Wording 2.0/14 Consistent Wording Across Displays 2.0/15 Consistent Grammatical Structure 2.0/16 Minimal Use of Abbreviation 2.0/17 Common Abbreviations 2.0/18 Simple Abbreviation Rule 2.0/19 Distinctive Abbreviations 2.0/20 Minimal Punctuation of Abbreviations 2.0/21 Dictionary of Abbreviations ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.12.1/1 Conventional Text Display 2.1/2 Printing Lengthy Text Displays 2.1/3 Consistent Text Format 2.1/4 Adequate Display Capacity 2.1/5 Text Displayed in Wide Columns 2.1/6 Conventional Use of Mixed Case 2.1/7 Separation of Paragraphs 2.1/8 Consistent Word Spacing 2.1/9 Minimal Hyphenation 2.1/10 Conventional Punctuation 2.1/11 Clarity of Wording 2.1/12 Sentences Begin with Main Topic 2.1/13 Simple Sentence Structure 2.1/14 Concise Wording 2.1/15 Distinct Wording 2.1/16 Affirmative Sentences 2.1/17 Active Voice 2.1/18 Temporal Sequence 2.1/19 Lists for Related Items 2.1/20 Single-Column List Format 2.1/21 Marking Multiline Items in a List 2.1/22 Arabic Numerals for Numbered Items 2.1/23 Logical List Ordering 2.1/24 Vertical Ordering in Multiple Columns 2.1/25 Hierarchic Structure for Long Lists 2.1/26 Abbreviations Defined in Text 2.1/27 Highlighting Text 2.1/28 Combining Text with Other Data 2.1/29 Placing Figures Near Their Citations ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.22.2/1 Forms for Related Data 2.2/2 Visually Distinctive Data Fields 2.2/3 Data Field Labeling 2.2/4 Descriptive Wording of Labels 2.2/5 Consistent Wording of Labels 2.2/6 Distinctive Wording of Labels 2.2/7 Consistent Label Location 2.2/8 Distinctive Label Format 2.2/9 Labels Close to Data Fields 2.2/10 Labeling Units of Measurement 2.2/11 Consistent Format Across Displays 2.2/12 Form Compatible for Data Entry and Display 2.2/13 Consistent Format Within Data Fields 2.2/14 Partitioning Long Data Items 2.2/15 Distinguishing Blanks from Nulls ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.32.3/1 Tables for Data Comparison 2.3/2 Logical Organization 2.3/3 Table Access by Row and Column 2.3/4 Tables Referenced by First Column 2.3/5 Items Paired for Direct Comparison 2.3/6 Row and Column Labels 2.3/7 Consistent Label Format 2.3/8 Distinctive Labeling 2.3/9 Numbered Items Start with 1 2.3/10 Repeated Elements in Hierarchic Numbering 2.3/11 Labeling Units of Measurement 2.3/12 Consistent Column Spacing 2.3/13 Column Scanning Cues 2.3/14 Row Scanning Cues 2.3/15 Justification of Alphabetic Data 2.3/16 Justification of Numeric Data 2.3/17 Maintaining Significant Zeros ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.42.4/1 Graphic Displays 2.4/2 Data Comparison 2.4/3 Monitoring Data Change 2.4/4 Consistency 2.4/5 Only Necessary Information Displayed 2.4/6 Highlighting Critical Data 2.4/7 Reference Index or Baseline 2.4/8 Text Annotation 2.4/9 Data Annotation 2.4/10 Consistent Annotation Format 2.4/11 Normal Orientation for Labels 2.4/12 Standard Symbols 2.4/13 Pictorial Symbols 2.4/14 Simple Texture Codes 2.4/15 Zooming for Display Expansion 2.4/16 Show Changing Scale 2.4/17 Show Overview Position of Visible Section 2.4/18 Animation for Dynamic Display 2.4/19 Highlighting by Animation 2.4/20 Printing Graphic Displays ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.12.4.1/1 Scaling Conventions 2.4.1/2 Consistent Scaling 2.4.1/3 Labeling Axes 2.4.1/4 Linear Scaling 2.4.1/5 Scaling in Standard Intervals 2.4.1/6 Numeric Scales Start at Zero 2.4.1/7 Restricted Use of Broken Axes 2.4.1/8 Duplicate Axes 2.4.1/9 Single Scale Only 2.4.1/10 Scaling Against a Reference Index 2.4.1/11 Aids for Scale Interpolation 2.4.1/12 Unobtrusive Grids 2.4.1/13 Restricted Use of Three-Dimensional Scaling ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.22.4.2/1 Scatterplots 2.4.2/2 Highlighting 2.4.2/3 Grouping Scatterplots to Show Multiple Relations 2.4.2/4 Interactive Analysis of Grouped Scatterplots ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.32.4.3/1 Curves and Line Graphs 2.4.3/2 Comparing Curves 2.4.3/3 Labeling Curves 2.4.3/4 Compatible Ordering in Legends 2.4.3/5 Highlighting 2.4.3/6 Line Coding to Distinguish Curves 2.4.3/7 Consistent Line Codes 2.4.3/8 Broken Lines for Projected Curves 2.4.3/9 Reference Index 2.4.3/10 Repeating Display of Cyclic Data 2.4.3/11 Direct Display of Differences 2.4.3/12 Surface Charts 2.4.3/13 Ordering Data in Surface Charts 2.4.3/14 Labeling Surface Charts 2.4.3/15 Cumulative Curves ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.42.4.4/1 Bar Graphs 2.4.4/2 Histograms (Step Charts) 2.4.4/3 Consistent Orientation of Bars 2.4.4/4 Bar Spacing 2.4.4/5 Reference Index 2.4.4/6 Highlighting 2.4.4/7 Paired or Overlapped Bars 2.4.4/8 Labeling Paired Bars 2.4.4/9 Stacked or Segmented Bars 2.4.4/10 Ordering Data in Stacked Bars 2.4.4/11 Restricted Use of Icons ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.52.4.5/1 Restricted Use of Pie Charts 2.4.5/2 Labeling Pie Charts 2.4.5/3 Numeric Labels 2.4.5/4 Highlighting ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.62.4.6/1 Pictures 2.4.6/2 Diagrams 2.4.6/3 Linking Sectional Diagrams 2.4.6/4 Highlighting 2.4.6/5 Rotation 2.4.6/6 Aids for Pictorial Analysis ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.72.4.7/1 Flowcharts 2.4.7/2 Flowcharts to Aid Problem Solving 2.4.7/3 Logical Ordering of Steps 2.4.7/4 Ordering to Minimize Path Length 2.4.7/5 Conventional Path Orientation 2.4.7/6 Consistent Coding of Elements 2.4.7/7 Conventional Use of Arrows 2.4.7/8 Highlighting 2.4.7/9 Single Decision at Each Step 2.4.7/10 Logical Ordering of Options 2.4.7/11 Consistent Ordering of Options 2.4.7/12 Consistent Wording ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.4.82.4.8/1 Maps 2.4.8/2 Consistent Orientation 2.4.8/3 Consistent Projection 2.4.8/4 Labeling Maps 2.4.8/5 Consistent Positioning of Labels 2.4.8/6 Area Coding 2.4.8/7 Tonal Codes 2.4.8/8 Ordered Coding 2.4.8/9 Highlighting 2.4.8/10 Panning for Flexible Display Framing 2.4.8/11 Show Overview Position of Visible Section 2.4.8/12 Aiding Distance Judgments 2.4.8/13 Aids for Analyzing Maps 2.4.8/14 Mapping Nongeographic Data 2.4.8/15 Situation Displays 2.4.8/16 Indicating Data Change 2.4.8/17 Selectable Data Categories 2.4.8/18 Stable Reference for Changing Data ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.52.5/1 Consistent Format 2.5/2 Distinctive Display Elements 2.5/3 Spacing to Structure Displays 2.5/4 Paging Crowded Displays 2.5/5 Related Data on Same Page 2.5/6 Page Labeling 2.5/7 Integrated Display 2.5/8 User-Defined Data Windows 2.5/9 Adequate Window Size 2.5/10 Display Title at Top 2.5/11 Command Entry, Prompts, Messages at Bottom 2.5/12 Logical Data Organization 2.5/13 Grouping for Data Comparison 2.5/14 Data Grouped by Sequence of Use 2.5/15 Data Grouped by Function 2.5/16 Data Grouped by Importance 2.5/17 Data Grouped by Frequency 2.5/18 Data Grouped Alphabetically or Chronologically ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.62.6/1 Highlighting Critical Data 2.6/2 Removing Highlighting 2.6/3 Coding by Data Category 2.6/4 Meaningful Codes 2.6/5 Familiar Coding Conventions 2.6/6 Definition of Display Codes 2.6/7 Consistent Coding Across Displays 2.6/8 Alphanumeric Coding 2.6/9 Consistent Case in Alphabetic Coding 2.6/10 Combining Letters and Numbers 2.6/11 Short Codes 2.6/12 Special Symbols 2.6/13 Consistent Use of Special Symbols 2.6/14 Markers Close to Words Marked 2.6/15 Shape Coding 2.6/16 Establishing Standards for Shape Coding 2.6/17 Line Coding 2.6/18 Underlining for Emphasis 2.6/19 Coding by Line Length 2.6/20 Coding by Line Direction 2.6/21 Limited Use of Size Coding 2.6/22 Adequate Differences in Size 2.6/23 Limited Use of Brightness Coding 2.6/24 Brightness Inversion 2.6/25 Color Coding for Relative Values 2.6/26 Color Coding for Data Categories 2.6/27 Easily Discriminable Colors 2.6/28 Conservative Use of Color 2.6/29 Adding Color to Formatted Displays 2.6/30 Redundant Color Coding 2.6/31 Unique Assignment of Color Codes 2.6/32 Conventional Assignment of Color Codes 2.6/33 Brightness and Saturation to Draw Attention 2.6/34 Saturated Blue for Background Color 2.6/35 Blink Coding 2.6/36 Blinking Marker Symbols 2.6/37 Optimal Blink Rate 2.6/38 Coding with Texture, Focus, Motion 2.6/39 Auditory Coding 2.6/40 Distinctive Auditory Coding 2.6/41 Voice Coding 2.6/42 Coding Synthesized Voice Alarms ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.72.7/1 Flexible Display Control by User ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.7.12.7.1/1 User Selection of Data for Display 2.7.1/2 Display Identification Labels 2.7.1/3 Meaningful Display Labels 2.7.1/4 Consistent Format for Display Labels 2.7.1/5 Selectable Data Categories 2.7.1/6 Fast Response to Display Request 2.7.1/7 Signaling Completion of Display Output 2.7.1/8 Regenerating Changed Data 2.7.1/9 Initial Erasure to Replace Changed Data 2.7.1/10 Nondestructive Overlay 2.7.1/11 Printing Displays Locally ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.7.22.7.2/1 Integrated Display 2.7.2/2 Easy Paging 2.7.2/3 Continuous Numbering in Multipage Lists 2.7.2/4 Labels for Multipage Tables 2.7.2/5 Annotating Display of Continued Data 2.7.2/6 Numbering Display Pages 2.7.2/7 Consistent Orientation - Panning vs. Scrolling 2.7.2/8 Panning with Free Cursor Movement 2.7.2/9 Functional Labeling for Display Framing 2.7.2/10 Labeling Panning Functions 2.7.2/11 Labeling Scrolling Functions 2.7.2/12 Panning for Flexible Display Framing 2.7.2/13 Zooming for Display Expansion 2.7.2/14 Show Changing Scale 2.7.2/15 Show Overview Position of Visible Section 2.7.2/16 Framing Integrally for All Data 2.7.2/17 Return to Normal Display Coverage ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.7.32.7.3/1 Automatic Display Update 2.7.3/2 Highlighting Changed Data 2.7.3/3 Readability of Changing Data 2.7.3/4 Visual Integration of Changing Graphics 2.7.3/5 Display Freeze 2.7.3/6 Labeling Display Freeze 2.7.3/7 Signaling Changes to Frozen Data 2.7.3/8 Resuming Update After Display Freeze 2.7.3/9 Prediction Display ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.7.42.7.4/1 Temporary Suppression of Displayed Data 2.7.4/2 Labeling Display Suppression 2.7.4/3 Signaling Changes to Suppressed Data 2.7.4/4 Resuming Display of Suppressed Data ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.7.52.7.5/1 Temporary Window Overlays 2.7.5/2 Predefined Windows 2.7.5/3 User-Specified Windows 2.7.5/4 Consistent Window Control 2.7.5/5 Easy Suppression of Window Overlays 2.7.5/6 Labeling Windows 2.7.5/7 Indicate Active Window 2.7.5/8 Easy Shifting Among Windows 2.7.5/9 Consistent Control Within Windows 2.7.5/10 Nondestructive Overlay ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗2.82.8/1 Flexible Design for Data Display </span><span class="style1"></span></text>
</content>
<content>
<layer>card</layer>
<id>26</id>
<text><span class="style1">.0 General 2.1 Text 2.2 Data Forms 2.3 Tables 2.4 Graphics</span><span class="style23"> t</span><span class="style1">2.5 Format 2.6 Coding 2.7 Display Control </span><span class="style23">t</span><span class="style1">2.8 Design Change </span></text>
</content>
<content>
<layer>card</layer>
<id>27</id>
<text>2.4 Graphics - General 2.4.1 Graphics - Scaling 2.4.2 Graphics - Scatterplots 2.4.3 Graphics - Curves and Line Graphs 2.4.4 Graphics - Bar Graphs 2.4.5 Graphics - Pie Charts 2.4.6 Graphics - Pictures and Diagrams 2.4.7 Graphics - Flowcharts 2.4.8 Graphics - Maps and Situation Displays </text>
</content>
<content>
<layer>card</layer>
<id>29</id>
<text>2.7 Display Control - General2.7.1 Display Control - Selection 2.7.2 Display Control - Framing 2.7.3 Display Control - Update 2.7.4 Display Control - Suppression 2.7.5 Display Control - Window Overlays </text>
</content>
<name>Data Display</name>
<script></script>
</card>
card_4711.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<content>
<layer>card</layer>
<id>21</id>
<text>┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.01.0/1 Data Entered Only Once1.0/2 Entry via Primary Display 1.0/3 Feedback During Data Entry 1.0/4 Fast Response 1.0/5 Single Method for Entering Data 1.0/6 Defined Display Areas for Data Entry 1.0/7 Consistent Method for Data Change 1.0/8 User-Paced Data Entry 1.0/9 Explicit ENTER Action 1.0/10 ENTER Key Labeling 1.0/11 Explicit CANCEL Action 1.0/12 Feedback for Completion of Data Entry 1.0/13 Feedback for Repetitive Data Entries 1.0/14 Feedback when Changing Data 1.0/15 Keeping Data Items Short 1.0/16 Partitioning Long Data Items 1.0/17 Optional Abbreviation 1.0/18 Distinctive Abbreviation 1.0/19 Simple Abbreviation Rule 1.0/20 Minimal Exceptions to Abbreviation Rule 1.0/21 Minimal Deviation from Abbreviation Rule 1.0/22 Fixed Abbreviation Length 1.0/23 Clarifying Unrecognized Abbreviations 1.0/24 Prompting Data Entry 1.0/25 Character Entry via Single Keystroke 1.0/26 Minimal Shift Keying 1.0/27 Upper and Lower Case Equivalent 1.0/28 Decimal Point Optional 1.0/29 Leading Zeros Optional 1.0/30 Single and Multiple Blanks Equivalent 1.0/31 Aids for Entering Hierarchic Data 1.0/32 Speech Input 1.0/33 Limited Vocabulary for Speech Input 1.0/34 Phonetically Distinct Vocabulary for Speech Input 1.0/35 Easy Error Correction for Speech Input 1.0/36 Alternative Entries for Speech Input 1.0/37 PAUSE and CONTINUE Options for Speech Input ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.11.1/1 Distinctive Cursor 1.1/2 Nonobscuring Cursor 1.1/3 Precise Pointing 1.1/4 Explicit Activation 1.1/5 Fast Acknowledgement of Entry 1.1/6 Stable Cursor 1.1/7 Responsive Cursor Control 1.1/8 Consistent Incremental Positioning 1.1/9 Variable Step Size 1.1/10 Proportional Spacing 1.1/11 Continuous Cursor Positioning 1.1/12 Direct Pointing 1.1/13 Large Pointing Area for Option Selection 1.1/14 Cursor Control at Keyboard 1.1/15 Compatible Control of Cursor Movement 1.1/16 Minimal Use of Multiple Cursors 1.1/17 Distinctive Multiple Cursors 1.1/18 Distinctive Control of Multiple Cursors 1.1/19 Compatible Control of Multiple Cursors 1.1/20 Consistent HOME Position 1.1/21 Consistent Cursor Placement 1.1/22 Easy Cursor Movement to Data Fields 1.1/23 Display Format Protection 1.1/24 Data Entry Independent of Cursor Placement ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.21.2/1 Analog Entry of Estimated Direction 1.2/2 Keyed Entry of Quantified Direction ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.31.3/1 Adequate Display Capacity 1.3/2 Editing Capabilities During Text Entry 1.3/3 Free Cursor Movement 1.3/4 Control Entries Distinct from Text 1.3/5 Natural Units of Text 1.3/6 Control Entry Based on Units of Text 1.3/7 Highlighting Specified Text 1.3/8 Cursor Movement by Units of Text 1.3/9 String Search 1.3/10 Upper and Lower Case Equivalent in Search 1.3/11 Specifying Case in Search 1.3/12 Global Search and Replace 1.3/13 Case in Global Search and Replace 1.3/14 Automatic Pagination Aids 1.3/15 User Control of Pagination 1.3/16 Controlling Integrity of Text Units 1.3/17 Automatic Line Break 1.3/18 Consistent Word Spacing 1.3/19 Hyphenation by Users 1.3/20 Format Control by User 1.3/21 Establishing Predefined Formats 1.3/22 Storing User-Defined Formats 1.3/23 Moving Text 1.3/24 Storing Frequently Used Text 1.3/25 Necessary Data Displayed 1.3/26 Text Distinct from Annotation 1.3/27 Text Displayed as Printed 1.3/28 Flexible Printing Options 1.3/29 Information on Printing Status 1.3/30 Auditory Signals for Alerting Users 1.3/31 Protecting Text During Page Overruns 1.3/32 Confirming Actions in DELETE Mode 1.3/33 Reversible Actions 1.3/34 User Confirmation of Editing Changes ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.41.4/1 Combined Entry of Related Data 1.4/2 Flexible Interrupt 1.4/3 Minimal Use of Delimiters 1.4/4 Standard Delimiter Character 1.4/5 Data Field Labels 1.4/6 Consistent Labeling 1.4/7 Protected Labels 1.4/8 Labels Close to Data Fields 1.4/9 Standard Symbol for Prompting Entry 1.4/10 Marking Field Boundaries 1.4/11 Prompting Field Length 1.4/12 Marking Required and Optional Data Fields 1.4/13 Field Markers Not Entered with Data 1.4/14 Automatic Justification of Variable-Length Entries 1.4/15 Explicit Tabbing to Data Fields 1.4/16 Distinctive Label Format 1.4/17 Consistent Label Format 1.4/18 Label Punctuation as Entry Cue 1.4/19 Informative Labels 1.4/20 Data Format Cueing in Labels 1.4/21 Labeling Units of Measurement 1.4/22 Familiar Units of Measurement 1.4/23 Alternative Units of Measurement 1.4/24 Form Compatible for Data Entry and Display 1.4/25 Form Compatible with Source Documents 1.4/26 Minimal Cursor Positioning 1.4/27 Data Items in Logical Order 1.4/28 Automatic Cursor Placement ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.51.5/1 Tables for Related Data Sets 1.5/2 Distinctive Labels 1.5/3 Informative Labels 1.5/4 Tabbing within Rows 1.5/5 Tabbing within Columns 1.5/6 Automatic Justification of Entries 1.5/7 Justification of Numeric Entries 1.5/8 Maintaining Significant Zeros 1.5/9 Aiding Entry of Duplicative Data 1.5/10 Row Scanning Cues ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.61.6/1 Pointing 1.6/2 Distinctive Cursor 1.6/3 Easy Cursor Positioning 1.6/4 Confirming Cursor Position 1.6/5 Zooming for Precise Positioning 1.6/6 Selecting Graphic Elements 1.6/7 Highlighting Selected Elements 1.6/8 Changing Position (Translation) 1.6/9 Deleting Elements 1.6/10 Selecting from Displayed Attributes 1.6/11 Selecting Colors 1.6/12 Displaying Current Attributes 1.6/13 Changing Attributes 1.6/14 Consistent Method for Attribute Selection 1.6/15 Easy Storage and Retrieval 1.6/16 Naming Displays and Elements 1.6/17 Automatic Data Registration 1.6/18 Aids for Entering Hierarchic Data 1.6/19 Automatic Data Validation ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.6.11.6.1/1 Automated Data Plotting 1.6.1/2 Plotting Stored Data 1.6.1/3 Predefined Graphic Formats 1.6.1/4 Aids for Graph Construction 1.6.1/5 Aids for Scaling 1.6.1/6 Computer Derivation of Graphic Data ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.6.21.6.2/1 Drawing Lines 1.6.2/2 Rubberbanding 1.6.2/3 Aiding Line Connection 1.6.2/4 Grid Reference for Alignment 1.6.2/5 Changing Grid Intervals 1.6.2/6 Constraint for Vertical and Horizontal Lines 1.6.2/7 Specifying Line Relations 1.6.2/8 Drawing Figures 1.6.2/9 Alternative Methods for Drawing Figures 1.6.2/10 Changing Size 1.6.2/11 Enlargement for Symbol Drawing 1.6.2/12 Copying Elements 1.6.2/13 Rotating Elements 1.6.2/14 Reflection of Elements 1.6.2/15 Grouping Elements 1.6.2/16 Merging Elements 1.6.2/17 Filling Enclosed Areas 1.6.2/18 Automatic Figure Completion 1.6.2/19 Stored Models ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.71.7/1 Automatic Data Validation 1.7/2 Accepting Correct Entries 1.7/3 Non-Disruptive Error Messages 1.7/4 Deferral of Required Data Entry 1.7/5 Reminder of Deferred Entry 1.7/6 Timely Validation of Sequential Transactions 1.7/7 Optional Item-by-Item Validation ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.81.8/1 Default Values 1.8/2 Defaults for Sequential Entries 1.8/3 User Definition of Default Values 1.8/4 Display of Default Values 1.8/5 Easy Confirmation to Enter Default Values 1.8/6 Temporary Replacement of Default Values 1.8/7 Automatic Generation of Routine Data 1.8/8 Automatic Computation of Derived Data 1.8/9 User Review of Prior Entries 1.8/10 Automatic Entry of Redundant Data 1.8/11 Automatic Cross-File Updating 1.8/12 Aids for Entering Hierarchic Data ┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗┬╗1.91.9/1 Flexible Design for Data Entry</text>
</content>
<content>
<layer>card</layer>
<id>26</id>
<text><span class="style1">.0 General 1.1 Position Designation 1.2 Direction Designation 1.3 Text 1.4 Data Forms 1.5 Tables 1.6 Graphics</span><span class="style23"> t</span><span class="style1">1.7 Data Validation 1.8 Other Data Processing 1.9 Design Change </span></text>
</content>
<content>
<layer>card</layer>
<id>27</id>
<text>1.6 Graphics - General 1.6.1 Graphics - Plotting Data 1.6.2 Graphics - Drawing </text>
</content>
<name>Data Entry</name>
<script></script>
</card>
card_5436.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput word 2 of the clickline into lineNoput word 6 of the clickline into fieldNoput word 1 of line lineNo of card field fieldNo into sectionNumif sectionNum is empty then exit mouseUpselect line lineNo of card field fieldNopush cardvisual effect iris closego card hashSection(sectionNum) of stack "BRUIT∆SAM Guidelines" ¬in a new windowif not(the result is empty) thenanswer "Sorry, could not find that Guideline :-("end ifset the cursor to handend mouseUp</script>
</part>
<part>
<id>2</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>6</left>
<top>153</top>
<right>57</right>
<bottom>203</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>8981</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Return</name>
<script>on mouseUppop cardend mouseUp</script>
</part>
<part>
<id>3</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>154</left>
<top>23</top>
<right>332</right>
<bottom>48</bottom>
</rect>
<style>rectangle</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Avant Garde</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>find</name>
<script>on returnInFieldsend mouseup to card button "Do Search…"end returnInField</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>349</left>
<top>20</top>
<right>451</right>
<bottom>50</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Do Search…</name>
<script>on mouseUpput empty into card field "findList"put card field "find" into findWords-- strip leading and trailing spaces-- put StripChars( space, findWords ) into findWords2if findWords is empty thenanswer "No words to search!"set the hilite of me to falseexit mouseupend ifif (number of chars in findWords) < 2 thenanswer "Words must be greater than 1 character"set the hilite of me to falseexit mouseupend ifset the hilite of me to trueset cursor to busyput "Searching: Please wait… "put card field "contents1" into CONTENTSput card field "contents2" after CONTENTSget SEARCH(CONTENTS,findWords,false,all)put it into findResif findRes is not empty thenrepeat with j = 1 to (number of lines in findRes)put "Searching: Found" && jset cursor to busyput line (item 1 of line j of findRes) of CONTENTS & return ¬after card field "findList"end repeatend ifhide msg boxif card field "findList" is empty then answer "Search words not found"set the hilite of me to falseend mouseUp</script>
</part>
<part>
<id>5</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>162</left>
<top>63</top>
<right>504</right>
<bottom>124</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>10</textSize>
<textStyle>plain</textStyle>
<textHeight>13</textHeight>
<name>contents1</name>
<script></script>
</part>
<part>
<id>7</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>166</left>
<top>132</top>
<right>506</right>
<bottom>196</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>contents2</name>
<script></script>
</part>
<content>
<layer>card</layer>
<id>5</id>
<text>1.0/1 Data Entered Only Once1.0/2 Entry via Primary Display 1.0/3 Feedback During Data Entry 1.0/4 Fast Response 1.0/5 Single Method for Entering Data 1.0/6 Defined Display Areas for Data Entry 1.0/7 Consistent Method for Data Change 1.0/8 User-Paced Data Entry 1.0/9 Explicit ENTER Action 1.0/10 ENTER Key Labeling 1.0/11 Explicit CANCEL Action 1.0/12 Feedback for Completion of Data Entry 1.0/13 Feedback for Repetitive Data Entries 1.0/14 Feedback when Changing Data 1.0/15 Keeping Data Items Short 1.0/16 Partitioning Long Data Items 1.0/17 Optional Abbreviation 1.0/18 Distinctive Abbreviation 1.0/19 Simple Abbreviation Rule 1.0/20 Minimal Exceptions to Abbreviation Rule 1.0/21 Minimal Deviation from Abbreviation Rule 1.0/22 Fixed Abbreviation Length 1.0/23 Clarifying Unrecognized Abbreviations 1.0/24 Prompting Data Entry 1.0/25 Character Entry via Single Keystroke 1.0/26 Minimal Shift Keying 1.0/27 Upper and Lower Case Equivalent 1.0/28 Decimal Point Optional 1.0/29 Leading Zeros Optional 1.0/30 Single and Multiple Blanks Equivalent 1.0/31 Aids for Entering Hierarchic Data 1.0/32 Speech Input 1.0/33 Limited Vocabulary for Speech Input 1.0/34 Phonetically Distinct Vocabulary for Speech Input 1.0/35 Easy Error Correction for Speech Input 1.0/36 Alternative Entries for Speech Input 1.0/37 PAUSE and CONTINUE Options for Speech Input 1.1/1 Distinctive Cursor 1.1/2 Nonobscuring Cursor 1.1/3 Precise Pointing 1.1/4 Explicit Activation 1.1/5 Fast Acknowledgement of Entry 1.1/6 Stable Cursor 1.1/7 Responsive Cursor Control 1.1/8 Consistent Incremental Positioning 1.1/9 Variable Step Size 1.1/10 Proportional Spacing 1.1/11 Continuous Cursor Positioning 1.1/12 Direct Pointing 1.1/13 Large Pointing Area for Option Selection 1.1/14 Cursor Control at Keyboard 1.1/15 Compatible Control of Cursor Movement 1.1/16 Minimal Use of Multiple Cursors 1.1/17 Distinctive Multiple Cursors 1.1/18 Distinctive Control of Multiple Cursors 1.1/19 Compatible Control of Multiple Cursors 1.1/20 Consistent HOME Position 1.1/21 Consistent Cursor Placement 1.1/22 Easy Cursor Movement to Data Fields 1.1/23 Display Format Protection 1.1/24 Data Entry Independent of Cursor Placement 1.2/1 Analog Entry of Estimated Direction 1.2/2 Keyed Entry of Quantified Direction 1.3/1 Adequate Display Capacity 1.3/2 Editing Capabilities During Text Entry 1.3/3 Free Cursor Movement 1.3/4 Control Entries Distinct from Text 1.3/5 Natural Units of Text 1.3/6 Control Entry Based on Units of Text 1.3/7 Highlighting Specified Text 1.3/8 Cursor Movement by Units of Text 1.3/9 String Search 1.3/10 Upper and Lower Case Equivalent in Search 1.3/11 Specifying Case in Search 1.3/12 Global Search and Replace 1.3/13 Case in Global Search and Replace 1.3/14 Automatic Pagination Aids 1.3/15 User Control of Pagination 1.3/16 Controlling Integrity of Text Units 1.3/17 Automatic Line Break 1.3/18 Consistent Word Spacing 1.3/19 Hyphenation by Users 1.3/20 Format Control by User 1.3/21 Establishing Predefined Formats 1.3/22 Storing User-Defined Formats 1.3/23 Moving Text 1.3/24 Storing Frequently Used Text 1.3/25 Necessary Data Displayed 1.3/26 Text Distinct from Annotation 1.3/27 Text Displayed as Printed 1.3/28 Flexible Printing Options 1.3/29 Information on Printing Status 1.3/30 Auditory Signals for Alerting Users 1.3/31 Protecting Text During Page Overruns 1.3/32 Confirming Actions in DELETE Mode 1.3/33 Reversible Actions 1.3/34 User Confirmation of Editing Changes 1.4/1 Combined Entry of Related Data 1.4/2 Flexible Interrupt 1.4/3 Minimal Use of Delimiters 1.4/4 Standard Delimiter Character 1.4/5 Data Field Labels 1.4/6 Consistent Labeling 1.4/7 Protected Labels 1.4/8 Labels Close to Data Fields 1.4/9 Standard Symbol for Prompting Entry 1.4/10 Marking Field Boundaries 1.4/11 Prompting Field Length 1.4/12 Marking Required and Optional Data Fields 1.4/13 Field Markers Not Entered with Data 1.4/14 Automatic Justification of Variable-Length Entries 1.4/15 Explicit Tabbing to Data Fields 1.4/16 Distinctive Label Format 1.4/17 Consistent Label Format 1.4/18 Label Punctuation as Entry Cue 1.4/19 Informative Labels 1.4/20 Data Format Cueing in Labels 1.4/21 Labeling Units of Measurement 1.4/22 Familiar Units of Measurement 1.4/23 Alternative Units of Measurement 1.4/24 Form Compatible for Data Entry and Display 1.4/25 Form Compatible with Source Documents 1.4/26 Minimal Cursor Positioning 1.4/27 Data Items in Logical Order 1.4/28 Automatic Cursor Placement 1.5/1 Tables for Related Data Sets 1.5/2 Distinctive Labels 1.5/3 Informative Labels 1.5/4 Tabbing within Rows 1.5/5 Tabbing within Columns 1.5/6 Automatic Justification of Entries 1.5/7 Justification of Numeric Entries 1.5/8 Maintaining Significant Zeros 1.5/9 Aiding Entry of Duplicative Data 1.5/10 Row Scanning Cues 1.6/1 Pointing 1.6/2 Distinctive Cursor 1.6/3 Easy Cursor Positioning 1.6/4 Confirming Cursor Position 1.6/5 Zooming for Precise Positioning 1.6/6 Selecting Graphic Elements 1.6/7 Highlighting Selected Elements 1.6/8 Changing Position (Translation) 1.6/9 Deleting Elements 1.6/10 Selecting from Displayed Attributes 1.6/11 Selecting Colors 1.6/12 Displaying Current Attributes 1.6/13 Changing Attributes 1.6/14 Consistent Method for Attribute Selection 1.6/15 Easy Storage and Retrieval 1.6/16 Naming Displays and Elements 1.6/17 Automatic Data Registration 1.6/18 Aids for Entering Hierarchic Data 1.6/19 Automatic Data Validation 1.6.1/1 Automated Data Plotting 1.6.1/2 Plotting Stored Data 1.6.1/3 Predefined Graphic Formats 1.6.1/4 Aids for Graph Construction 1.6.1/5 Aids for Scaling 1.6.1/6 Computer Derivation of Graphic Data 1.6.2/1 Drawing Lines 1.6.2/2 Rubberbanding 1.6.2/3 Aiding Line Connection 1.6.2/4 Grid Reference for Alignment 1.6.2/5 Changing Grid Intervals 1.6.2/6 Constraint for Vertical and Horizontal Lines 1.6.2/7 Specifying Line Relations 1.6.2/8 Drawing Figures 1.6.2/9 Alternative Methods for Drawing Figures 1.6.2/10 Changing Size 1.6.2/11 Enlargement for Symbol Drawing 1.6.2/12 Copying Elements 1.6.2/13 Rotating Elements 1.6.2/14 Reflection of Elements 1.6.2/15 Grouping Elements 1.6.2/16 Merging Elements 1.6.2/17 Filling Enclosed Areas 1.6.2/18 Automatic Figure Completion 1.6.2/19 Stored Models 1.7/1 Automatic Data Validation 1.7/2 Accepting Correct Entries 1.7/3 Non-Disruptive Error Messages 1.7/4 Deferral of Required Data Entry 1.7/5 Reminder of Deferred Entry 1.7/6 Timely Validation of Sequential Transactions 1.7/7 Optional Item-by-Item Validation 1.8/1 Default Values 1.8/2 Defaults for Sequential Entries 1.8/3 User Definition of Default Values 1.8/4 Display of Default Values 1.8/5 Easy Confirmation to Enter Default Values 1.8/6 Temporary Replacement of Default Values 1.8/7 Automatic Generation of Routine Data 1.8/8 Automatic Computation of Derived Data 1.8/9 User Review of Prior Entries 1.8/10 Automatic Entry of Redundant Data 1.8/11 Automatic Cross-File Updating 1.8/12 Aids for Entering Hierarchic Data 1.9/1 Flexible Design for Data Entry 2.0/1 Necessary Data Displayed 2.0/2 Only Necessary Data Displayed 2.0/3 Data Displayed in Usable Form 2.0/4 Data Display Consistent with User Conventions 2.0/5 Establishing Display Standards 2.0/6 Consistent Display Format 2.0/7 Display Consistent with Entry Requirements 2.0/8 User Control of Data Display 2.0/9 User Changes to Displayed Data 2.0/10 Protection of Displayed Data 2.0/11 Context for Displayed Data 2.0/12 Familiar Wording 2.0/13 Consistent Wording 2.0/14 Consistent Wording Across Displays 2.0/15 Consistent Grammatical Structure 2.0/16 Minimal Use of Abbreviation 2.0/17 Common Abbreviations 2.0/18 Simple Abbreviation Rule 2.0/19 Distinctive Abbreviations 2.0/20 Minimal Punctuation of Abbreviations 2.0/21 Dictionary of Abbreviations 2.1/1 Conventional Text Display 2.1/2 Printing Lengthy Text Displays 2.1/3 Consistent Text Format 2.1/4 Adequate Display Capacity 2.1/5 Text Displayed in Wide Columns 2.1/6 Conventional Use of Mixed Case 2.1/7 Separation of Paragraphs 2.1/8 Consistent Word Spacing 2.1/9 Minimal Hyphenation 2.1/10 Conventional Punctuation 2.1/11 Clarity of Wording 2.1/12 Sentences Begin with Main Topic 2.1/13 Simple Sentence Structure 2.1/14 Concise Wording 2.1/15 Distinct Wording 2.1/16 Affirmative Sentences 2.1/17 Active Voice 2.1/18 Temporal Sequence 2.1/19 Lists for Related Items 2.1/20 Single-Column List Format 2.1/21 Marking Multiline Items in a List 2.1/22 Arabic Numerals for Numbered Items 2.1/23 Logical List Ordering 2.1/24 Vertical Ordering in Multiple Columns 2.1/25 Hierarchic Structure for Long Lists 2.1/26 Abbreviations Defined in Text 2.1/27 Highlighting Text 2.1/28 Combining Text with Other Data 2.1/29 Placing Figures Near Their Citations 2.2/1 Forms for Related Data 2.2/2 Visually Distinctive Data Fields 2.2/3 Data Field Labeling 2.2/4 Descriptive Wording of Labels 2.2/5 Consistent Wording of Labels 2.2/6 Distinctive Wording of Labels 2.2/7 Consistent Label Location 2.2/8 Distinctive Label Format 2.2/9 Labels Close to Data Fields 2.2/10 Labeling Units of Measurement 2.2/11 Consistent Format Across Displays 2.2/12 Form Compatible for Data Entry and Display 2.2/13 Consistent Format Within Data Fields 2.2/14 Partitioning Long Data Items 2.2/15 Distinguishing Blanks from Nulls 2.3/1 Tables for Data Comparison 2.3/2 Logical Organization 2.3/3 Table Access by Row and Column 2.3/4 Tables Referenced by First Column 2.3/5 Items Paired for Direct Comparison 2.3/6 Row and Column Labels 2.3/7 Consistent Label Format 2.3/8 Distinctive Labeling 2.3/9 Numbered Items Start with 1 2.3/10 Repeated Elements in Hierarchic Numbering 2.3/11 Labeling Units of Measurement 2.3/12 Consistent Column Spacing 2.3/13 Column Scanning Cues 2.3/14 Row Scanning Cues 2.3/15 Justification of Alphabetic Data 2.3/16 Justification of Numeric Data 2.3/17 Maintaining Significant Zeros 2.4/1 Graphic Displays 2.4/2 Data Comparison 2.4/3 Monitoring Data Change 2.4/4 Consistency 2.4/5 Only Necessary Information Displayed 2.4/6 Highlighting Critical Data 2.4/7 Reference Index or Baseline 2.4/8 Text Annotation 2.4/9 Data Annotation 2.4/10 Consistent Annotation Format 2.4/11 Normal Orientation for Labels 2.4/12 Standard Symbols 2.4/13 Pictorial Symbols 2.4/14 Simple Texture Codes 2.4/15 Zooming for Display Expansion 2.4/16 Show Changing Scale 2.4/17 Show Overview Position of Visible Section 2.4/18 Animation for Dynamic Display 2.4/19 Highlighting by Animation 2.4/20 Printing Graphic Displays 2.4.1/1 Scaling Conventions 2.4.1/2 Consistent Scaling 2.4.1/3 Labeling Axes 2.4.1/4 Linear Scaling 2.4.1/5 Scaling in Standard Intervals 2.4.1/6 Numeric Scales Start at Zero 2.4.1/7 Restricted Use of Broken Axes 2.4.1/8 Duplicate Axes 2.4.1/9 Single Scale Only 2.4.1/10 Scaling Against a Reference Index 2.4.1/11 Aids for Scale Interpolation 2.4.1/12 Unobtrusive Grids 2.4.1/13 Restricted Use of Three-Dimensional Scaling 2.4.2/1 Scatterplots 2.4.2/2 Highlighting 2.4.2/3 Grouping Scatterplots to Show Multiple Relations 2.4.2/4 Interactive Analysis of Grouped Scatterplots 2.4.3/1 Curves and Line Graphs 2.4.3/2 Comparing Curves 2.4.3/3 Labeling Curves 2.4.3/4 Compatible Ordering in Legends 2.4.3/5 Highlighting 2.4.3/6 Line Coding to Distinguish Curves 2.4.3/7 Consistent Line Codes 2.4.3/8 Broken Lines for Projected Curves 2.4.3/9 Reference Index 2.4.3/10 Repeating Display of Cyclic Data 2.4.3/11 Direct Display of Differences 2.4.3/12 Surface Charts 2.4.3/13 Ordering Data in Surface Charts 2.4.3/14 Labeling Surface Charts 2.4.3/15 Cumulative Curves 2.4.4/1 Bar Graphs 2.4.4/2 Histograms (Step Charts) 2.4.4/3 Consistent Orientation of Bars 2.4.4/4 Bar Spacing 2.4.4/5 Reference Index 2.4.4/6 Highlighting 2.4.4/7 Paired or Overlapped Bars 2.4.4/8 Labeling Paired Bars 2.4.4/9 Stacked or Segmented Bars 2.4.4/10 Ordering Data in Stacked Bars 2.4.4/11 Restricted Use of Icons 2.4.5/1 Restricted Use of Pie Charts 2.4.5/2 Labeling Pie Charts 2.4.5/3 Numeric Labels 2.4.5/4 Highlighting 2.4.6/1 Pictures 2.4.6/2 Diagrams 2.4.6/3 Linking Sectional Diagrams 2.4.6/4 Highlighting 2.4.6/5 Rotation 2.4.6/6 Aids for Pictorial Analysis 2.4.7/1 Flowcharts 2.4.7/2 Flowcharts to Aid Problem Solving 2.4.7/3 Logical Ordering of Steps 2.4.7/4 Ordering to Minimize Path Length 2.4.7/5 Conventional Path Orientation 2.4.7/6 Consistent Coding of Elements 2.4.7/7 Conventional Use of Arrows 2.4.7/8 Highlighting 2.4.7/9 Single Decision at Each Step 2.4.7/10 Logical Ordering of Options 2.4.7/11 Consistent Ordering of Options 2.4.7/12 Consistent Wording 2.4.8/1 Maps 2.4.8/2 Consistent Orientation 2.4.8/3 Consistent Projection 2.4.8/4 Labeling Maps 2.4.8/5 Consistent Positioning of Labels 2.4.8/6 Area Coding 2.4.8/7 Tonal Codes 2.4.8/8 Ordered Coding 2.4.8/9 Highlighting 2.4.8/10 Panning for Flexible Display Framing 2.4.8/11 Show Overview Position of Visible Section 2.4.8/12 Aiding Distance Judgments 2.4.8/13 Aids for Analyzing Maps 2.4.8/14 Mapping Nongeographic Data 2.4.8/15 Situation Displays 2.4.8/16 Indicating Data Change 2.4.8/17 Selectable Data Categories 2.4.8/18 Stable Reference for Changing Data 2.5/1 Consistent Format 2.5/2 Distinctive Display Elements 2.5/3 Spacing to Structure Displays 2.5/4 Paging Crowded Displays 2.5/5 Related Data on Same Page 2.5/6 Page Labeling 2.5/7 Integrated Display 2.5/8 User-Defined Data Windows 2.5/9 Adequate Window Size 2.5/10 Display Title at Top 2.5/11 Command Entry, Prompts, Messages at Bottom 2.5/12 Logical Data Organization 2.5/13 Grouping for Data Comparison 2.5/14 Data Grouped by Sequence of Use 2.5/15 Data Grouped by Function 2.5/16 Data Grouped by Importance 2.5/17 Data Grouped by Frequency 2.5/18 Data Grouped Alphabetically or Chronologically 2.6/1 Highlighting Critical Data 2.6/2 Removing Highlighting 2.6/3 Coding by Data Category 2.6/4 Meaningful Codes 2.6/5 Familiar Coding Conventions 2.6/6 Definition of Display Codes 2.6/7 Consistent Coding Across Displays 2.6/8 Alphanumeric Coding 2.6/9 Consistent Case in Alphabetic Coding 2.6/10 Combining Letters and Numbers 2.6/11 Short Codes 2.6/12 Special Symbols 2.6/13 Consistent Use of Special Symbols 2.6/14 Markers Close to Words Marked 2.6/15 Shape Coding 2.6/16 Establishing Standards for Shape Coding 2.6/17 Line Coding 2.6/18 Underlining for Emphasis 2.6/19 Coding by Line Length 2.6/20 Coding by Line Direction 2.6/21 Limited Use of Size Coding 2.6/22 Adequate Differences in Size 2.6/23 Limited Use of Brightness Coding 2.6/24 Brightness Inversion 2.6/25 Color Coding for Relative Values 2.6/26 Color Coding for Data Categories 2.6/27 Easily Discriminable Colors 2.6/28 Conservative Use of Color 2.6/29 Adding Color to Formatted Displays 2.6/30 Redundant Color Coding 2.6/31 Unique Assignment of Color Codes 2.6/32 Conventional Assignment of Color Codes 2.6/33 Brightness and Saturation to Draw Attention 2.6/34 Saturated Blue for Background Color 2.6/35 Blink Coding 2.6/36 Blinking Marker Symbols 2.6/37 Optimal Blink Rate 2.6/38 Coding with Texture, Focus, Motion 2.6/39 Auditory Coding 2.6/40 Distinctive Auditory Coding 2.6/41 Voice Coding 2.6/42 Coding Synthesized Voice Alarms 2.7/1 Flexible Display Control by User 2.7.1/1 User Selection of Data for Display 2.7.1/2 Display Identification Labels 2.7.1/3 Meaningful Display Labels 2.7.1/4 Consistent Format for Display Labels 2.7.1/5 Selectable Data Categories 2.7.1/6 Fast Response to Display Request 2.7.1/7 Signaling Completion of Display Output 2.7.1/8 Regenerating Changed Data 2.7.1/9 Initial Erasure to Replace Changed Data 2.7.1/10 Nondestructive Overlay 2.7.1/11 Printing Displays Locally 2.7.2/1 Integrated Display 2.7.2/2 Easy Paging 2.7.2/3 Continuous Numbering in Multipage Lists 2.7.2/4 Labels for Multipage Tables 2.7.2/5 Annotating Display of Continued Data 2.7.2/6 Numbering Display Pages 2.7.2/7 Consistent Orientation - Panning vs. Scrolling 2.7.2/8 Panning with Free Cursor Movement 2.7.2/9 Functional Labeling for Display Framing 2.7.2/10 Labeling Panning Functions 2.7.2/11 Labeling Scrolling Functions 2.7.2/12 Panning for Flexible Display Framing 2.7.2/13 Zooming for Display Expansion 2.7.2/14 Show Changing Scale 2.7.2/15 Show Overview Position of Visible Section 2.7.2/16 Framing Integrally for All Data 2.7.2/17 Return to Normal Display Coverage 2.7.3/1 Automatic Display Update 2.7.3/2 Highlighting Changed Data 2.7.3/3 Readability of Changing Data 2.7.3/4 Visual Integration of Changing Graphics 2.7.3/5 Display Freeze 2.7.3/6 Labeling Display Freeze 2.7.3/7 Signaling Changes to Frozen Data 2.7.3/8 Resuming Update After Display Freeze 2.7.3/9 Prediction Display 2.7.4/1 Temporary Suppression of Displayed Data 2.7.4/2 Labeling Display Suppression 2.7.4/3 Signaling Changes to Suppressed Data 2.7.4/4 Resuming Display of Suppressed Data 2.7.5/1 Temporary Window Overlays 2.7.5/2 Predefined Windows 2.7.5/3 User-Specified Windows 2.7.5/4 Consistent Window Control 2.7.5/5 Easy Suppression of Window Overlays 2.7.5/6 Labeling Windows 2.7.5/7 Indicate Active Window 2.7.5/8 Easy Shifting Among Windows 2.7.5/9 Consistent Control Within Windows 2.7.5/10 Nondestructive Overlay 2.8/1 Flexible Design for Data Display 3.0/1 Flexible Sequence Control 3.0/2 Minimal User Actions 3.0/3 Control Matched to User Skill 3.0/4 User Initiative in Sequence Control 3.0/5 Control by Explicit User Action 3.0/6 Consistent User Actions 3.0/7 Logical Transaction Sequences 3.0/8 Distinctive Display of Control Information 3.0/9 Displayed Context 3.0/10 Consistent Terminology for Sequence Control 3.0/11 Congruent Names for Control Functions 3.0/12 Upper and Lower Case Equivalent 3.0/13 Wording Consistent with User Guidance 3.0/14 Feedback for Control Entries 3.0/15 Indicating Completion of Processing 3.0/16 Compatibility with User Expectations 3.0/17 User-Paced Sequence Control 3.0/18 Appropriate Computer Response Time 3.0/19 Control Availability 3.0/20 Indicating Control Lockout 3.0/21 Interrupt to End Control Lockout 3.0/22 Control by Simultaneous Users 3.1/1 Dialogue Matched to Task and User 3.1/2 Appropriate Computer Response Time 3.1.1/1 Question-and-Answer Dialogue 3.1.1/2 Questions Displayed Singly 3.1.1/3 Recapitulating Prior Answers 3.1.1/4 Sequence Compatible with Source Documents 3.1.2/1 Form Filling for Data Entry 3.1.2/2 Form Filling for Control Entry 3.1.2/3 Defaults for Control Entry 3.1.2/4 Consistent Format for Control Forms 3.1.3/1 Menu Selection 3.1.3/2 Single Selection Per Menu 3.1.3/3 Single-Column List Format 3.1.3/4 Menu Selection by Pointing 3.1.3/5 Large Pointing Area for Option Selection 3.1.3/6 Dual Activation for Pointing 3.1.3/7 Menu Selection by Keyed Entry 3.1.3/8 Standard Area for Code Entry 3.1.3/9 Feedback for Menu Selection 3.1.3/10 Explanatory Title for Menu 3.1.3/11 Menu Options Worded as Commands 3.1.3/12 Option Wording Consistent with Command Language 3.1.3/13 Letter Codes for Menu Selection 3.1.3/14 Consistent Coding of Menu Options 3.1.3/15 Standard Symbol for Prompting Entry 3.1.3/16 Explicit Option Display 3.1.3/17 Complete Display of Menu Options 3.1.3/18 Menu Options Dependent on Context 3.1.3/19 Consistent Display of Menu Options 3.1.3/20 Menus Distinct from Other Displayed Information 3.1.3/21 Logical Ordering of Menu Options 3.1.3/22 Logical Grouping of Menu Options 3.1.3/23 Logical Ordering of Grouped Options 3.1.3/24 Labeling Grouped Options 3.1.3/25 Hierarchic Menus for Sequential Selection 3.1.3/26 General Menu 3.1.3/27 Minimal Steps in Sequential Menu Selection 3.1.3/28 Easy Selection of Important Options 3.1.3/29 Automatic Cursor Placement 3.1.3/30 Indicating Current Position in Menu Structure 3.1.3/31 Control Options Distinct from Menu Branching 3.1.3/32 Consistent Design of Hierarchic Menus 3.1.3/33 Return to Higher-Level Menus 3.1.3/34 Return to General Menu 3.1.3/35 By-Passing Menu Selection with Command Entry 3.1.3/36 Stacking Menu Selections 3.1.4/1 Function Keys for Critical Control Entries 3.1.4/2 Function Keys for Frequent Control Entries 3.1.4/3 Function Keys for Interim Control Entries 3.1.4/4 Distinctive Labeling of Function Keys 3.1.4/5 Labeling Multifunction Keys 3.1.4/6 Single Keying for Frequent Functions 3.1.4/7 Logical Pairing of Double-Keyed Functions 3.1.4/8 Consistent Logic for Double Keying 3.1.4/9 Single Activation of Function Keys 3.1.4/10 Feedback for Function Key Activation 3.1.4/11 Indicating Active Function Keys 3.1.4/12 Disabling Unneeded Function Keys 3.1.4/13 Single Key for Continuous Functions 3.1.4/14 Consistent Assignment of Function Keys 3.1.4/15 Consistent Functions in Different Operational Modes 3.1.4/16 Easy Return to Base-Level Functions 3.1.4/17 Distinctive Location 3.1.4/18 Layout Compatible with Use 3.1.5/1 Command Language 3.1.5/2 Standard Display Area for Command Entry 3.1.5/3 Functional Wording 3.1.5/4 Layered Command Language 3.1.5/5 Meaningful Command Names 3.1.5/6 Familiar Wording 3.1.5/7 Consistent Wording of Commands 3.1.5/8 Distinctive Meaning for Commands 3.1.5/9 Distinctive Spelling for Commands 3.1.5/10 User-Assigned Command Names 3.1.5/11 User-Requested Prompts 3.1.5/12 General List of Commands 3.1.5/13 Command Stacking 3.1.5/14 User Definition of Macro Commands 3.1.5/15 Minimal Punctuation 3.1.5/16 Standard Delimiter 3.1.5/17 Ignoring Blanks in Command Entry 3.1.5/18 Abbreviation of Commands 3.1.5/19 Standard Techniques for Command Editing 3.1.5/20 Interpreting Misspelled Commands 3.1.5/21 Recognizing Command Synonyms 3.1.5/22 Recognizing Alternative Syntax 3.1.5/23 Correcting Command Entry Errors 3.1.5/24 Replacing Erroneous Commands 3.1.5/25 Reviewing Destructive Commands 3.1.6/1 Query Language 3.1.6/2 Natural Organization of Data 3.1.6/3 Coherent Representation of Data Organization 3.1.6/4 Task-Oriented Wording 3.1.6/5 Flexible Query Formulation 3.1.6/6 Minimal Need for Quantifiers 3.1.6/7 Logic to Link Queries 3.1.6/8 Linking Sequential Queries 3.1.6/9 Confirming Large-Scale Retrieval 3.1.7/1 Constrained Natural Language 3.1.8/1 Control of Graphic Data 3.1.8/2 Graphic Control Aids for Casual Users 3.1.8/3 Iconic Menus 3.1.8/4 Supplementary Verbal Labels 3.1.8/5 Direct Manipulation 3.1.8/6 Graphic Display of Control Context 3.1.8/7 Graphic Display of Control Prompting 3.2/1 User Control in Transaction Selection 3.2/2 General List of Control Options 3.2/3 Organization and Labeling of Listed Options 3.2/4 Indicating Appropriate Control Options 3.2/5 Prompting Control Entries 3.2/6 Cursor Placement for Pointing at Options 3.2/7 Cursor Placement for Keyed Entry of Options 3.2/8 Displaying Option Codes 3.2/9 Task-Oriented Wording for Options 3.2/10 Only Available Options Offered 3.2/11 Indicating Control Defaults 3.2/12 Consistent CONTINUE Option 3.2/13 Stacked Control Entries 3.2/14 Consistent Order in Entry Stacking 3.2/15 Abbreviation in Entry Stacking 3.2/16 Minimal Punctuation of Stacked Entries 3.2/17 Standard Delimiter in Entry Stacking 3.2/18 User Definition of Macro Commands 3.2/19 User-Specified Transaction Timing 3.3/1 User Interruption of Transactions 3.3/2 Distinctive Interrupt Options 3.3/3 CANCEL Option 3.3/4 BACKUP Option 3.3/5 REVIEW Option 3.3/6 RESTART Option 3.3/7 END Option 3.3/8 PAUSE and CONTINUE Options 3.3/9 Indicating PAUSE Status 3.3/10 SUSPEND Option 3.3/11 Indicating SUSPEND Status 3.4/1 Defining Context for Users 3.4/2 Context Established by Prior Entries 3.4/3 Record of Prior Entries 3.4/4 Display of Operational Mode 3.4/5 Display of Control Parameters 3.4/6 Highlighting Selected Data 3.4/7 Consistent Display of Context Information 3.5/1 Appropriate Response to All Entries 3.5/2 Command Editing 3.5/3 Prompting Command Correction 3.5/4 Errors in Stacked Commands 3.5/5 Partial Execution of Stacked Commands 3.5/6 Explicit Entry of Corrections 3.5/7 User Confirmation of Destructive Entries 3.5/8 User Warned of Potential Data Loss 3.5/9 Distinctive CONFIRM Action 3.5/10 UNDO to Reverse Control Actions 3.5/11 Preventing Data Loss at LOG-OFF 3.5/12 Immediate Data Correction 3.5/13 Flexible BACKUP for Error Correction 3.6/1 Alarm Definition by Users 3.6/2 Distinctive and Consistent Alarms 3.6/3 Alarm Acknowledgment 3.6/4 Alarm Reset 3.6/5 Special Acknowledgment of Critical Alarms 3.7/1 Flexible Design for Sequence Control </text>
</content>
<content>
<layer>card</layer>
<id>7</id>
<text>4.0/1 Standard Procedures 4.0/2 Explicit User Actions 4.0/3 Separate LOG-ON Procedure 4.0/4 Display of Guidance Information 4.0/5 Only Necessary Information Displayed4.0/6 Consistent Display Format 4.0/7 Consistent Format for User Guidance 4.0/8 Distinctive Format for User Guidance 4.0/9 Distinctive Cursor 4.0/10 Clear Control Labels 4.0/11 Clear Data Labels 4.0/12 Highlighting Critical User Guidance 4.0/13 Consistent Coding Conventions 4.0/14 Familiar Coding Conventions 4.0/15 Consistent Wording 4.0/16 Familiar Wording 4.0/17 Task-Oriented Wording 4.0/18 Wording Consistent with Control Entry 4.0/19 Speaking Directly to Users 4.0/20 Affirmative Statements 4.0/21 Active Voice 4.0/22 Temporal Sequence 4.0/23 Consistent Grammatical Structure 4.0/24 Flexible User Guidance 4.0/25 Easy Ways to Get Guidance 4.0/26 Speech Output 4.0/27 Limited Number of Spoken Messages 4.0/28 Simple Spoken Messages 4.0/29 Distinctive Spoken Warnings 4.1/1 Indicating Status 4.1/2 Automatic LOG-ON Display 4.1/3 LOG-ON Delay 4.1/4 Keyboard Lock 4.1/5 Operational Mode 4.1/6 Other Users 4.1/7 System Load 4.1/8 External Systems 4.1/9 Date and Time Signals 4.1/10 Alarm Settings 4.2/1 Consistent Feedback 4.2/2 Fast Response 4.2/3 Feedback for Control Entries 4.2/4 Indicating Completion of Processing 4.2/5 Feedback for Print Requests 4.2/6 Display Identification 4.2/7 Identifying Multipage Displays 4.2/8 Indicating Operational Mode 4.2/9 Indicating Option Selection 4.2/10 Indicating Item Selection 4.2/11 Feedback for User Interrupt 4.3/1 Informative Error Messages 4.3/2 Specific Error Messages 4.3/3 Task-Oriented Error Messages 4.3/4 Advisory Error Messages 4.3/5 Brief Error Messages 4.3/6 Neutral Wording for Error Messages 4.3/7 Multilevel Error Messages 4.3/8 Multiple Error Messages 4.3/9 Indicating Repeated Errors 4.3/10 Non-Disruptive Error Messages 4.3/11 Appropriate Response Time for Error Messages 4.3/12 Documenting Error Messages 4.3/13 Cursor Placement Following Error 4.3/14 Displaying Erroneous Entries 4.3/15 User Editing of Entry Errors 4.3/16 Removing Error Messages 4.3/17 Cautionary Messages 4.3/18 User Confirmation of Destructive Entries 4.3/19 Alarm Coding 4.4/1 Guidance Information Always Available 4.4/2 General List of Control Options 4.4/3 Logical Menu Structure 4.4/4 Hierarchic Menus 4.4/5 Guidance for Sequence Control 4.4/6 Transaction-Specific Option Display 4.4/7 Prompting Entries 4.4/8 Standard Display Location for Prompting 4.4/9 Consistent Format for Prompts 4.4/10 Standard Symbol for Prompting Entry 4.4/11 Concise Wording of Prompts 4.4/12 User-Requested Prompts 4.4/13 Displayed Context 4.4/14 Maintaining Context for Data Entry 4.4/15 Cues for Prompting Data Entry 4.4/16 Consistent Cursor Positioning 4.4/17 On-Line System Guidance 4.4/18 Index of Data 4.4/19 Index of Commands 4.4/20 Dictionary of Abbreviations 4.4/21 Definition of Display Codes 4.4/22 Record of Past Transactions 4.4/23 HELP 4.4/24 Standard Action to Request HELP 4.4/25 Task-Oriented HELP 4.4/26 Clarifying HELP Requests 4.4/27 Synonyms for Standard Terminology 4.4/28 Multilevel HELP 4.4/29 Browsing HELP 4.4/30 On-Line Training 4.4/31 Flexible Training 4.4/32 Adaptive Training 4.5/1 User Performance Measurement 4.5/2 Notifying Users 4.5/3 Transaction Records 4.5/4 Data Access Records 4.5/5 Records of Program Use 4.5/6 Error Records 4.5/7 HELP Records 4.6/1 Flexible Design for User Guidance 4.6/2 Notifying Users of Design Changes 5.0/1 Functional Integration 5.0/2 Functional Wording 5.0/3 Consistent Procedures 5.0/4 Minimal Memory Load on User 5.0/5 Minimal User Actions 5.0/6 Control by Explicit User Action 5.0/7 Flexible User Control 5.0/8 Interrupt 5.0/9 Flexible Message Filing 5.0/10 Message Highlighting 5.1/1 Message Composition Compatible with Data Entry 5.1/2 User-Designed Message Formats5.1/3 Unformatted Text 5.1/4 Stored Message Forms 5.1/5 Automatic Message Formatting 5.1/6 Automatic Text Formatting 5.1/7 Data Forms 5.1/8 Tables and Graphics 5.1/9 Flexible Data Specification 5.1/10 Incorporate Existing Files 5.1/11 Incorporate Other Messages 5.1/12 Variable Message Length 5.1/13 Saving Draft Messages 5.2/1 Destination Selection 5.2/2 Standard Address Header 5.2/3 Prompting Address Entry 5.2/4 Address Directory 5.2/5 Aids for Directory Search 5.2/6 Extracting Directory Addresses 5.2/7 User-Assigned Nicknames for Addressing 5.2/8 System Distribution Lists 5.2/9 Access to Distribution List Information 5.2/10 Informal Distribution Lists 5.2/11 Lists Within Lists 5.2/12 Modifying Distribution Lists 5.2/13 Automatic Expansion of Partial Addresses 5.2/14 Automatic Address Checking 5.2/15 Addressing Replies to Messages Received 5.2/16 Editing Address Headers 5.2/17 Single Occurrence of Address 5.2/18 Serial Distribution 5.2/19 Redistributing Received Messages 5.3/1 User-Initiated Transmission 5.3/2 User Review Before Transmission 5.3/3 Optional Message Display 5.3/4 Computer-Initiated Transmission 5.3/5 Information About Communication Status 5.3/6 Sender Identification 5.3/7 Assignment of Priority 5.3/8 Automatic Queuing for Transmission 5.3/9 Deferring Message Transmission 5.3/10 Transmission at Specified Date/Time 5.3/11 Return Receipt 5.3/12 Cancel Transmission 5.3/13 Printing Messages 5.4/1 Automatic Protection of Transmitted Data 5.4/2 Automatic Feedback 5.4/3 User Specification of Feedback 5.4/4 Send Single Copy 5.4/5 Queuing Failed Transmissions 5.4/6 Saving Undelivered Messages 5.4/7 Notification of Transmission Failure 5.4/8 Message Recall 5.4/9 Automatic Record Keeping 5.5/1 Specifying Sources 5.5/2 Specifying Device Destination 5.5/3 Queuing Messages Received 5.5/4 Message Notification at LOG-ON 5.5/5 Nondisruptive Notification of Arriving Messages 5.5/6 Indicating Priority of Received Messages 5.5/7 Filters for Message Notification 5.5/8 Warning of Incompatible Format 5.5/9 Information about Queued Messages 5.5/10 Indicate Message Size 5.5/11 Specifying Format for Message Listings 5.5/12 User Review of Messages in Queue 5.5/13 Filters for Ordering Message Review 5.5/14 Message Review Compatible with Data Display 5.5/15 Labeling Received Messages5.5/16 Annotating Received Messages 5.5/17 Filters for Message Filing 5.5/18 Discarding Messages 5.6/1 Flexible Design for Data Transmission 6.0/1 Automated Security Measures 6.0/2 Warning of Threats to Security 6.0/3 Protection from Computer Failure 6.0/4 Protection from Interference by Other Users 6.0/5 Protection from Interrupts 6.0/6 Segregating Real from Simulated Data 6.0/7 Consistent Procedures 6.0/8 Appropriate Ease or Difficulty of User Actions 6.0/9 Control by Explicit User Action 6.0/10 User Review and Editing of Entries 6.0/11 Disabling Unneeded Controls 6.0/12 Protecting Physical Controls 6.0/13 Safe Defaults 6.0/14 Safe Response to Random Inputs 6.0/15 Explicit Action to Select Destructive Modes 6.0/16 Feedback for Mode Selection 6.0/17 Warning Users of Potential Data Loss 6.0/18 User Confirmation of Destructive Actions 6.0/19 Distinctive CONFIRM Action 6.0/20 Separate CONFIRM Action 6.0/21 Reversible Control Actions (UNDO) 6.1/1 Easy LOG-ON 6.1/2 Prompting LOG-ON 6.1/3 User Choice of Passwords 6.1/4 Changing Passwords 6.1/5 Private Entry of Passwords 6.1/6 Limiting Unsuccessful LOG-ON Attempts 6.1/7 Auxiliary Tests to Authenticate User Identity 6.1/8 Continuous Recognition of User Identity 6.2/1 Single Authorization for Data Access 6.2/2 Displayed Security Classification 6.2/3 Protecting Displayed Data 6.2/4 Indicating Read-Only Displays 6.2/5 Protecting Display Formats 6.2/6 Display Suppression for Security 6.2/7 Protecting Printed Data 6.2/8 Automatic Records of Data Access 6.2/9 Encryption 6.2/10 Ensuring Reversible Encryption 6.3/1 Single Authorization for Data Entry/Change 6.3/2 Protection from Data Change 6.3/3 Data Entry/Change Transaction Records 6.3/4 Simple Procedures 6.3/5 Explicit User Actions6.3/6 Single Entry of Related Data 6.3/7 Data Entry Independent of Cursor Placement 6.3/8 Editing Data Before Entry 6.3/9 Immediate Error Correction 6.3/10 Editing Entries After Error Detection 6.3/11 Explicit Entry of Corrections 6.3/12 Flexible BACKUP for Error Correction 6.3/13 Data Verification by User Review 6.3/14 Automatic Data Generation 6.3/15 Displaying Default Values 6.3/16 Displaying Data to be Changed 6.3/17 Validating Data Changes 6.3/18 Cross Validation of Related Data 6.3/19 User Confirmation of Destructive Actions 6.3/20 Distinctive File Names 6.3/21 Segregating Real from Simulated Data 6.3/22 Preventing Data Loss at LOG-OFF 6.4/1 Automatic Protection of Transmitted Data 6.4/2 User Review of Data Before Transmission 6.4/3 Encrypting Messages 6.4/4 Saving Transmitted Data Until Receipt is Confirmed 6.4/5 Nondisruptive Notification of Messages Received 6.4/6 Authenticating Message Sources 6.4/7 Printing Messages 6.5/1 Flexible Design for Data Protection 6.5/2 Protection from Design Change </text>
</content>
<name>Search…</name>
<script></script>
</card>
card_5223.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUpput word 2 of the clickline into lineNoput word 6 of the clickline into fieldNoput word 1 of line lineNo of card field fieldNo into sectionNumif sectionNum is empty then exit mouseUpselect line lineNo of card field fieldNopush cardvisual effect iris closego card hashSection(sectionNum) of stack "BRUIT∆SAM Guidelines" ¬in a new windowif not(the result is empty) thenanswer "Sorry, could not find that Guideline :-("end ifset the cursor to handend mouseUp</script>
</part>
<part>
<id>3</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>421</left>
<top>68</top>
<right>505</right>
<bottom>96</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Clear All…</name>
<script>on mouseUpAnswer "Are you Sure?" with "Cancel","Yes"if it = "Yes" then put empty into card field "gather"end mouseUp</script>
</part>
<part>
<id>4</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>421</left>
<top>6</top>
<right>505</right>
<bottom>34</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Sort…</name>
<script>on mouseUpset cursor to busyput linesort(card field "gather") into card field "gather"set cursor to busyend mouseUp</script>
</part>
<part>
<id>5</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>421</left>
<top>37</top>
<right>505</right>
<bottom>65</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Unique…</name>
<script>on mouseUp--make sure it's sortedset cursor to busyput linesort(card field "gather") into card field "gather"set cursor to busyput empty into deleteList-- looprepeat with i = 2 to (the number of lines in card field "gather")set cursor to busyput word 1 of line i of card field "gather" into thisNumput word 1 of line (i-1) of card field "gather" into lastNumif thisNum = lastNum thenput i & "," after deleteListend ifend repeatrepeat with i = (number of items in deleteList) down to 1set cursor to busydelete line (item i of deleteList) of card field "gather"end repeatend mouseUp</script>
</part>
<part>
<id>6</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>62</left>
<top>158</top>
<right>323</right>
<bottom>180</bottom>
</rect>
<style>checkbox</style>
<showName> <true /> </showName>
<highlight> <true /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Always Gather "See Also" Guidelines</name>
<script>on mouseUpglobal gatherSEEALSOget the hilite of meset the hilite of me to (not it)put (not it) into gatherSEEALSOend mouseUp</script>
</part>
<part>
<id>7</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>421</left>
<top>100</top>
<right>505</right>
<bottom>128</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Delete…</name>
<script>on mouseUp--make sure it's sortedput linesort(card field "gather") into card field "gather"put card field "gather" into gTEXTif gTEXT is empty then exit MouseUpput ShowList(gTEXT,return,"Select Guideline(s) to remove",¬true,"OK,Cancel") into gRESULTif line 1 of gRESULT is "Cancel" then exit mouseUprepeat with i = (number of lines in gRESULT) down to 2delete line (item 2 of line i of gRESULT) of card field "gather"end repeatend mouseUp</script>
</part>
<part>
<id>8</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>421</left>
<top>132</top>
<right>505</right>
<bottom>160</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Export…</name>
<script>on mouseUpAnswer "What format?" with "Cancel","Plain Text","MS Word™"if it = "Cancel" then exit mouseUpif it = "Plain Text" then do exportTEXT "ttxt"if it = "MS Word™" then do exportTEXT "MSWD"end mouseUpon exportTEXT creatorglobal refTEXTif card field "gather" is empty thenanswer "There are no Guidelines gathered?"exit to hypercardend ifask file "Write Guidelines to:"put it into fileNameif fileName is empty then exit to hypercardput the hilite of card button 8 into exportREFput empty into refTEXTput empty into exportTEXT--make sure it's sortedset cursor to busyput linesort(card field "gather") into card field "gather"lock screenrepeat with i =1 to (the number of lines in card field "gather")set cursor to busyput "Exporting:" && (line i of card field "gather")put word 1 of line i of card field "gather" into sectionNumpush cardgo card hashSection(sectionNum) of stack "BRUIT∆SAM Guidelines"put field "Heading" & return after exportTEXTput field "Statement" & return after exportTEXTif exportREF and ¬(the textstyle of bg button "Reference…") is plain thenput "∆∆ Reference" & return after exportTEXTput field "Reference" & return after refTEXTput field "Reference" & return after exportTEXTend ifput return after exportTEXTpop cardend repeat-- process the Referencesif exportREF thenput return & "REFERENCES" & return & return after exportTEXT-- make the refTEXT contain unique entriesset cursor to busyput "Exporting: References"put linesort(refTEXT) into refTEXTput empty into deleteList-- looprepeat with i = 1 to (the number of lines in refTEXT)put line i of refTEXT into refTMPif refTMP contains "§" thenput char 1 to (offset("§",refTMP)-2) of refTMP into¬line i of refTEXTend ifend repeatrepeat with i = 2 to (the number of lines in refTEXT)put "Exporting: References" && iset cursor to busyput line i of refTEXT into thisRefput line (i-1) of refTEXT into lastRefif thisRef = lastRef thenput i & "," after deleteListend ifend repeatrepeat with i = (number of items in deleteList) down to 1put "Exporting: Removing duplicate References" && iset cursor to busydelete line (item i of deleteList) of refTEXTend repeat--repeat with i = 1 to (the number of lines in refTEXT)put line i of refTEXT into cardNameput "Exporting: References" && cardNamepush cardset the cursor to busygo card cardName of stack "BRUIT∆SAM Reference"put bg field "Reference" & return& return after exportTEXTpop card--end repeatend ifopen file fileNameput "∆∆∆∆∆∆ BRUIT∆SAM ∆∆∆∆∆∆ Start of Report ∆∆∆∆∆∆" ¬& return & return & return into headerput "∆∆∆∆∆∆ BRUIT∆SAM ∆∆∆∆∆∆ End of Report ∆∆∆∆∆∆" ¬& return into footerwrite (header & exportTEXT & footer) to file fileNameclose file fileName-- set type to TEXT and creator to TeachTextput SETCREATOR(fileName,"TEXT",creator) into errif err <> "OK" thenanswer "Error in Setting File attributes"end if--hide msg boxunlock screenend exportTEXT</script>
</part>
<part>
<id>9</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>62</left>
<top>181</top>
<right>323</right>
<bottom>203</bottom>
</rect>
<style>checkbox</style>
<showName> <true /> </showName>
<highlight> <true /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Include References in Export</name>
<script>on mouseUpget the hilite of meset the hilite of me to (not it)end mouseUp</script>
</part>
<name>Gather…</name>
<script></script>
</card>
card_9571.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseDownput word 2 of the clickline into lineNoput word 6 of the clickline into fieldNoput line lineNo of card field fieldNo into findLineif findLine is empty then exit mouseDownlock screenrepeat with i = 2 to 13hide card field iend repeatput (top of card field "section" + ((lineNo -1) * (the textHeight of ¬card field "section"-3))) + 4 into btnPointset the top of card button "Section-Hilite" to btnPointset the scroll of card field findLine to zeroshow card field findLineunlock screen with visual effect wipe rightend mouseDown</script>
</part>
<part>
<id>6</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>65</left>
<top>10</top>
<right>218</right>
<bottom>24</bottom>
</rect>
<style>transparent</style>
<showName> <false /> </showName>
<highlight> <true /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>section-hilite</name>
<script>on mouseDownsend mouseDown to card field "section"end mouseDown</script>
</part>
<part>
<id>7</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>Information Systems</name>
<script></script>
</part>
<part>
<id>8</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>user system interface</name>
<script></script>
</part>
<part>
<id>9</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>user interface software</name>
<script></script>
</part>
<part>
<id>10</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>significance of the ui</name>
<script></script>
</part>
<part>
<id>11</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>design practice</name>
<script></script>
</part>
<part>
<id>12</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>design guidelines</name>
<script></script>
</part>
<part>
<id>13</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>guidelines organization</name>
<script></script>
</part>
<part>
<id>14</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>applying the guidelines</name>
<script></script>
</part>
<part>
<id>15</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>role of the guidelines</name>
<script></script>
</part>
<part>
<id>16</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>introduction</name>
<script></script>
</part>
<part>
<id>17</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Palatino</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>acknowledgment</name>
<script></script>
</part>
<part>
<id>18</id>
<type>field</type>
<visible> <true /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <true /> </lockText>
<rect>
<left>223</left>
<top>6</top>
<right>507</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <true /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>executive summary</name>
<script></script>
</part>
<content>
<layer>card</layer>
<id>3</id>
<text>Executive SummaryAcknowledgmentIntroductionInformation SystemsUser System InterfaceUser Interface SoftwareSignificance of the UIDesign PracticeDesign GuidelinesGuidelines OrganizationApplying the GuidelinesRole of the Guidelines</text>
</content>
<content>
<layer>card</layer>
<id>7</id>
<text><span class="style31">NFORMATION SYSTEMS </span><span class="style25">Computers today are used for a broad range of applications. User interface design guidelines cannot be applied usefully in every case. Some computers may be embedded as components in larger systems, so that they communicate only with other computers and not directly with human users. When there is no user interface, then no user interface design guidelines are needed. Some computers are designed as general tools which can be adapted by skilled users for whatever purpose they desire. The particular tasks for which a general-purpose computer might be used are not defined in advance by the designer. Instead, a user must provide exact instructions to program the computer to perform any task at hand. The designer may try to ensure that the computer can process appropriate programming languages, but otherwise is not concerned with explicit design of a user interface. Other computer systems are designed to help particular users perform specific tasks. Such computer applications are referred to here as information systems. Applications of information systems range from relatively simple data entry and retrieval (e.g., airline reservations) through more complex monitoring and control tasks (inventory control, process control, air traffic control) to jobs requiring long-term analysis and planning. Military command, control and communication systems span that broad range of information system applications. To the extent that information systems support human users performing defined tasks, careful design of the user-system interface will be needed to ensure effective system operation. The guidelines proposed in this report are intended to improve user interface design for such information systems. Users of information systems interact with a computer in order to accomplish information handling tasks necessary to get their jobs done. They differ in ability, training and job experience. They may be keenly concerned with task performance, but may have little knowledge of (or interest in) the computers themselves. Design of the user-system interface must take account of those human factors. </span></text>
</content>
<content>
<layer>card</layer>
<id>8</id>
<text><span class="style31">SER-SYSTEM INTERFACE </span><span class="style25">What is the user-system interface? In common usage, the phrase is broadly defined to include all aspects of system design that affect system use (Smith, 1982a). This report, however, is concerned more narrowly with the user interface to computer-based information systems, i.e., with those aspects of system design that influence a user's participation in information handling tasks. This report focuses even more narrowly on those design features of the user interface that are implemented via software (i.e., the design of computer program logic) rather than hardware (the design of equipment). The guidelines proposed here are generally worded in terms of the functions that a user must perform, and the functional capabilities that a designer should provide, rather than the particular physical devices that might be used to implement those functions. Thus a particular guideline might deal with "pointing" as a function, with no necessary recommendation whether pointing should be accomplished via touch display or lightpen or any other physical device. It is obvious that software is not the only significant factor influencing user performance. Other aspects of user interface design are clearly important, including workstation design, physical display characteristics, keyboard layout, environmental factors such as illumination and noise, the design of paper forms and written documentation, user training courses, etc. To achieve a good user interface design, all of those factors must be designed with care. But designers must look elsewhere for advice on those topics. They are not covered in this report. </span></text>
</content>
<content>
<layer>card</layer>
<id>9</id>
<text><span class="style31">SER INTERFACE SOFTWARE </span><span class="style25">The significant role of user interface software in system design poses a special challenge to human factors practitioners, recognized early by Parsons (1970, page 169): </span><span class="style32"> . . . what sets data processing systems apart as a special breed? The function of each switch button, the functional arrangement among the buttons, the size and distribution of elements within a display are established not in the design of the equipment but in how the computer is programmed. Of even more consequence, the 'design' in the programs establishes the contents of processed data available to the operator and the visual relationships among the data. In combination with or in place of hardware, it can also establish the sequence of actions which the operator must use and the feedback to the operator concerning those actions. </span><span class="style25">Continuing concern for user interface software is suggested by phrases such as "software psychology" (cf. Shneiderman, 1980). But user interface design cannot be the concern only of the psychologist or the human factors specialist. It is a significant part of information system design that must engage the attention of system developers, designers, and ultimately system users as well. Those who look to the future of information systems predict that user interface design will become a specialty area; designers trained in both computer science and human factors will be employed to develop user interface software (Williges, 1984). User interface software can represent a sizable investment of programming effort during initial system development, and later when a system is upgraded. In a recent survey (Smith and Mosier, 1984b), information system designers were asked to estimate the percent of operational software devoted to implementing the user interface. Overall, the average estimate was that user interface design comprises 30 to 35 percent of operational software. Estimates for individual systems ranged from 3 to 100 percent, reflecting the fact that some computer systems require a much higher investment in user interface design than others, depending upon their purpose. </span></text>
</content>
<content>
<layer>card</layer>
<id>10</id>
<text><span class="style31">IGNIFICANCE OF THE USER INTERFACE </span><span class="style25">The design of user interface software is not only expensive and time-consuming, but it is also critical for effective system performance. To be sure, users can sometimes compensate for poor design with extra effort. Probably no single user interface design flaw, in itself, will cause system failure. But there is a limit to how well users can adapt to a poorly designed interface. As one deficiency is added to another, the cumulative negative effects may eventually result in system failure, poor performance, and/or user complaints. Outright system failure can be seen in systems that are underused, where use is optional, or are abandoned entirely. There may be retention of (or reversion to) manual data handling procedures, with little use of automated capabilities. When a system fails in this way, the result is disrupted operation, wasted time, effort and money, and failure to achieve the potential benefits of automated information handling. In a constrained environment, such as that of many military and commercial information systems, users may have little choice but to make do with whatever interface design is provided. There the symptoms of poor user interface design may appear in degraded performance. Frequent and/or serious errors in data handling may result from confusing user interface design. Tedious user procedures may slow data processing, resulting in longer queues at the checkout counter, the teller's window, the visa office, the truck dock, or any other workplace where the potential benefits of computer support are outweighed by an unintended increase in human effort. In situations where degradation in system performance is not so easily measured, symptoms of poor user interface design may appear as user complaints. The system may be described as hard to learn, or clumsy, tiring and slow to use. The users' view of a system is conditioned chiefly by experience with its interface. If the user interface is unsatisfactory, the users' view of the system will be negative regardless of any niceties of internal computer processing. A convincing demonstration of design improvement has been reported by Keister and Gallaway (1983). Those authors describe a data entry application in which relatively simple improvements to user interface software -- including selection and formatting of displayed data, consistency in wording and procedures, on-line user guidance, explicit error messages, re-entry rather than overtyping for data change, elimination of abbreviations, etc. -- resulted in significantly improved system performance. Data entry was accomplished 25 percent faster, and with 25 percent fewer errors. How can that kind of design improvement be achieved in general practice? </span></text>
</content>
<content>
<layer>card</layer>
<id>11</id>
<text><span class="style31">ESIGN PRACTICE </span><span class="style25">It seems fair to characterize current user interface software design as art rather than science, depending more upon individual judgment than systematic application of knowledge (Ramsey and Atwood, 1979; 1980). As an art, user interface design is best practiced by experts, by specialists experienced in the human engineering of computer systems. But such experts are not always available to help guide system development, and it is clear that they cannot personally guide every step of design. What is needed is some way to embody expert judgment in the form of explicit design guidelines. For military information systems, Military Specification MIL-H-48655B (1979) calls for a system development sequence starting with requirements analysis, functional specification and verification before any software design begins. The actual course of user interface software development will sometimes depart from that desired sequence. There may be no explicit attempt to determine user interface requirements. Specifications may include only rudimentary references to user interface design, with general statements that the system must be "easy to use". In the absence of effective guidance, both the design and implementation of user interface software may become the responsibility of programmers unfamiliar with operational requirements. Detection and correction of design flaws may occur only after system prototyping, when software changes are difficult to make. Human engineering standards and design handbooks have in the past been of little use to the software designer. The popular human factors design handbook by Woodson (1981) is typical. Its nearly 1000 pages include only three pages of general material on information processing, and there is no reference to computer systems in its index. MIL-STD-1472B (1974), for many years the major human engineering design standard for military system procurement, was concerned almost exclusively with hardware design and physical safety. In 1981, MIL-STD-1472 was published in a revised "C" version. That version included nine pages dealing with user interface software design, in a section titled "Personnel-Computer Interface". That material was later expanded to 19 pages, titled "User-Computer Interface", in a revision of MIL-STD-1472C (1983). Thus a beginning has been made, but much more is needed. The question is, what guidance can be offered for user interface software design? </span></text>
</content>
<content>
<layer>card</layer>
<id>12</id>
<text><span class="style31">ESIGN GUIDELINES </span><span class="style25">Until several years ago, there had been no serious attempt to integrate the scattered papers, articles and technical reports that constitute the literature of user-computer interaction. A first step was made, under sponsorship of the Office of Naval Research (ONR), in compilation of an extensive bibliography on this subject (Ramsey, Atwood and Kirshbaum, 1978). A significant follow-on effort culminated in publication by Ramsey and Atwood (1979) of a comprehensive summary of this literature. In reviewing the literature, it is apparent that most published reports dealing with the user-computer interface describe applications rather than design principles. A popular early book on the design of user-computer dialogues offered stimulating examples, covering a range of on-line applications, but was disappointing in its failure to emphasize design principles (Martin, 1973). The ONR bibliography cited above includes 564 items, but identifies only 17 as offering design guidelines. Although accepted principles for user interface design have not been available, some work has been accomplished toward that end. As experience has been gained in the use of on-line computer systems, some experts have attempted to set forth principles ("guidelines", "ground rules", "rules of thumb") for design of the user-computer interface. If experts cannot yet assert tested principles for user interface design, they might still offer sensible recommendations as a guide for designers. Military agencies are not the only organizations seeking guidelines for user interface design. There is keen interest in this topic within industrial and commercial organizations, and throughout the general community of people who develop and use information systems. David Penniman, writing for the User On-Line Interaction Group of the American Society for Information Sciences, has cited the need for "an interim set of guidelines for user interface design based on available literature and pending the development of better guidelines as our knowledge increases" (1979, page 2). Penniman goes on to remind us that interim guidelines are better than no guidelines at all. In a survey of people concerned with user interface design (Smith and Mosier, 1984b), respondents generally support Penniman's activist position. Given a choice between trying to develop a complete set of user interface guidelines now, when many of them must be based on judgment rather than experimental data, or else accepting only a partial set of guidelines based on evaluated research, most respondents would go with judgment now. It is clear, of course, that system developers cannot wait for future research data in making present design decisions. To meet current needs, several in-house handbooks have been published to guide user interface design within particular organizations (NASA, 1979; Galitz, 1980; Brown, Brown, Burkleo, Mangelsdorf, Olsen, and Perkins, 1983; Sidorsky, Parrish, Gates, and Munger, 1984). These in-house guidelines draw heavily from those in earlier publications, especially the influential IBM report by Engel and Granda (1975), as modified by the authors' own good judgment. The ESD/MITRE compilation of user interface design guidelines over the past several years has drawn from the work of our predecessors, and will help support the work of others to follow. Each year our guidelines compilation has grown larger. In this present report there are 944 guidelines. This compilation represents the most comprehensive guidance available for designing user interface software, and for that reason this report is recommended as a basic reference for developing information systems. </span></text>
</content>
<content>
<layer>card</layer>
<id>13</id>
<text><span class="style31">UIDELINES ORGANIZATION </span><span class="style25">In the numbered sections of this report, guidelines are organized within six functional areas of user-system interaction:</span><span class="style33">Section Functional Area Guidelines </span><span class="style25"> 1 Data Entry 199 2 Data Display 298 3 Sequence Control 184 4 User Guidance 110 5 Data Transmission 83 6 Data Protection 70 Each section of guidelines covers a different functional area of user-system interaction, although there is necessarily some overlap in topical coverage from one section to another. Within each section, guidelines are grouped by specific functions. Each function has its own numeric designator, as listed in the table of contents for this report. In adopting this functional organization, we have established a broad conceptual structure for dealing with the range of topics that must be considered in user interface design. Such a conceptual structure is urgently needed to help clarify discourse in this field. Each section of the guidelines begins with an introductory discussion of design issues relating to the general functional area. That discussion provides some perspective for the guidelines that follow. The discussion concludes with brief definitions of the various user interface functions covered in that section of the guidelines, along with an internal table of contents for that section, which may help to lead a reader directly to functions of immediate interest. Function definitions are repeated in boxed format to begin the listing of guidelines under each function. Those definitions should aid reader understanding of the material, and the boxed format will provide a notable visual indicator that a new series of guidelines has begun. The guidelines themselves are numbered sequentially under each function, in order to permit convenient referencing. Under any function there will usually be guidelines pertaining to various subordinate topics. Each guideline has been given a short title to indicate its particular subject matter. Sometimes one guideline may introduce a new topic and then be followed by several closely related guidelines. Each of those related guidelines has been marked with an plus sign next to its title. Following its number and title, each guideline is stated as a single sentence. Guidelines are worded as simply as possible, usually in general terms to permit broad application, but sometimes with contingent phrasing intended to define a more limited scope of application. In many instances, a stated guideline will be illustrated by one or more examples. When an example includes some sort of imagined computer output, such as an error message, prompt, menu, etc., that output has been marked with enclosing vertical strokes: </span><span class="style24"> | sample computer output | </span><span class="style25">There is no question that specific examples can help clarify a generally-worded guideline. Sometimes a reader will say, "I didn't really understand the guideline until I saw the example." But there is a potential hazard in examples. Because any example must be narrowly specific, a reader who relies on that example may interpret the guideline as having a narrower meaning than was intended. It is important to emphasize that examples are presented here only to illustrate the guidelines, and are not intended to limit the interpretation of guidelines. Where the validity of a guideline is contingent upon special circumstances, examples may be followed by noted exceptions. Those exceptions are intended to limit the interpretation of a guideline. Where further clarification of a guideline seems needed, examples and noted exceptions are followed by supplementary comments. Those comments may explain the reasoning behind a guideline, or suggest possible ways to interpret a guideline, or perhaps note relations between one guideline and another. Where a guideline has been derived from or is related in some way to other published reports, a reference note may be added citing author(s) and date. Complete citations for those references are listed following Section 6 of the guidelines. Where a guideline corresponds with other published design standards or guidelines, which is often the case, reference citations are given by letter codes. Those codes are explained in the reference list. Where a guideline is specifically related to guidelines in other sections, appropriate cross references are given. Those cross references permit an interested reader to explore how a particular topic is dealt with in different sections of the guidelines. Toward the back of this report, following the guidelines is the reference list. Following the reference list is a glossary. The glossary defines word usage in the guidelines, for those words that are used here differently or more narrowly than in the general literature on user interface design. There is no question that we need more consistent terminology in this field. Following the glossary is a list of the titles for all 944 guidelines, which may help a reader who is trying to find guidelines that pertain to a particular topic. Following the list of guideline titles, and concluding this report is a topical index of the guidelines material. That index is intended to help readers find guidelines on a particular subject, independently of the functional organization that has been imposed on the guidelines material. These notes on organization and format should serve to allow a student of the subject to skim the guidelines material and find information on different topics. For those readers who seek to apply the guidelines in software design, some further comments are needed. </span></text>
</content>
<content>
<layer>card</layer>
<id>14</id>
<text><span class="style31">PPLYING THE GUIDELINES </span><span class="style25">Not all of the guidelines proposed here can be applied in designing any particular system. For any particular system application, some of the guidelines will be relevant and some will not. In a recent survey of guidelines application (Mosier and Smith, 1986), respondents indicated that they actually applied only 40 percent of the guidelines published in a previous report. There is another problem to consider. Design guidelines such as those proposed here must be generally worded so that they might apply to many different system applications. Thus generally-worded guidelines must be translated into specific design rules before they can actually be applied. The process of selecting relevant guidelines for application and translating them into specific design rules is referred to here as "tailoring". Who will do this guidelines tailoring? It should be the joint responsibility of system analysts and human factors specialists assessing design requirements, of software designers assessing feasibility, and of their managers. It may also be helpful to include representatives of the intended system users in this process, to ensure that proposed design features will meet operational requirements. To simplify discussion, we shall call all of these persons "designers". As a first step in guidelines tailoring, a designer must review this report in order to identify those guidelines that are relevant. For example, if an application will require menus, then the 36 guidelines in Section 3.1.3 dealing with Menu Selection are potentially relevant. For a large information system, the list of relevant guidelines may be quite large. Once all relevant guidelines have been identified, a designer must review them and decide which ones actually to apply. There are two reasons why a designer might not wish to apply all relevant guidelines. First, for any given application some guidelines may conflict, and the designer must therefore choose which are more important. Second, budgetary and time restrictions may force the designer to apply only the most important guidelines -- those that promise to have the greatest effect on system usability. As noted above, because guidelines are intended for use on a variety of systems they are worded in general terms. Before a guideline can actually be applied it must be translated into specific design rules. For instance, a guideline which states that displays should be consistently formatted might be translated into design rules that specify where various display features should appear, such as the display title, prompts and other user guidance, error messages, command entries, etc. Any guideline can have different possible translations. A guideline which states that each display should be uniquely identified could be translated into a design rule that display titles will be bolded and centered in the top line of the display. Or it could be translated into a design rule that display titles will be capitalized in the upper left corner of the display. What would happen if guidelines were not translated into design rules, but instead were given directly to interface designers? If designers do not decide as a group what design rules will be used, then each designer will decide separately in the course of applying guidelines. The result will surely be an inconsistent design. After design rules have been specified for each selected guideline, those rules should be documented for reference by software designers and others involved in system development. Documentation of agreed rules, subject to periodic review and revision as necessary, will help coordinate the design process. Documented rules can then be applied consistently for a given application. With appropriate modifications, rules adopted for one application might later be used for other applications. In the course of design, it may be determined that a particular design rule cannot be used. Therefore, some means must be provided to deal with exceptions. If a design rule is not appropriate for one particular display, then an exception can be made by whoever has been appointed to make such decisions. But if a design rule cannot be implemented at all, perhaps due to other design constraints, then all designers for that particular system must be notified, and perhaps another design rule must be substituted. Finally, after the design is complete, it must be evaluated against the original design requirements to ensure that all design rules have indeed been followed. To help in the exception process and in the evaluation process, it may be useful to assign different weights to the various rules, indicating which are more important than others. Such weighting will help resolve the trade-offs that are an inevitable part of the design process. </span></text>
</content>
<content>
<layer>card</layer>
<id>15</id>
<text><span class="style31">OLE OF GUIDELINES IN SYSTEM DEVELOPMENT </span><span class="style25">If guidelines are applied in the way described here, there are some significant implications for the role of guidelines in system development. Generally stated guidelines should be offered to designers as a potential resource, rather than imposed as a contractual design standard (Smith, 1986). It is only specifically worded design rules that can be enforced, not guidelines. Design rules can be derived from the guidelines material, but that conversion from guidelines to rules should be performed as an integral part of the design process, serving to focus attention on critical design issues and to establish specific design requirements. Once agreed design rules are established, those rules can be maintained and enforced by the managers of system development projects. Specific design rules probably cannot be imposed effectively at the outset of system development by some external agency -- by a sponsoring organization or by a marketing group. It is the process of establishing design rules that should be imposed, rather than the rules themselves. A software design contractor might reasonably be required to establish rules for the design of user interface software, subject to review by the contracting agency. Available guidelines could be cited as a potentially useful reference for that purpose. Some other cautionary comments about the application of guidelines deserve consideration here. Guidelines in themselves cannot assure good design for a variety of reasons (Thimbleby, 1985). Guidelines cannot take the place of experience. An experienced designer, one skilled in the art, might do well without any guidelines. An inexperienced designer might do poorly even with guidelines. Few designers will find time to read an entire book of guidelines. If they do, they will find it difficult to digest and remember all of the material. If guidelines and/or the rules derived from guidelines are to be helpful, they must be kept continually available for ready reference. Guidelines cannot take the place of expert design consultants, or at least not entirely. A design expert will know more about a specific topic than can be presented in the guidelines. An expert will know what questions to ask, as well as many of the answers. An expert will know how to adapt generally-stated guidelines to the specific needs of a particular system design application. An expert will know how to trade off the competing demands of different guidelines, in terms of operational requirements. For maximum effectiveness, guideline tailoring must take place early in the design process before any actual design of user interface software. In order to tailor guidelines, designers must have a thorough understanding of task requirements and user characteristics. Thus task analysis is a necessary prerequisite of guidelines tailoring. The result of guidelines application will be a design for user interface software that may incorporate many good recommendations. However, even the most careful design will require testing with actual users in order to confirm the value of good features and discover what bad features may have been overlooked. Thus prototype testing must follow initial design, followed in turn by possible redesign and operational testing. Indeed, testing is so essential for ensuring good design that some experts advocate early creation of an operational prototype to evaluate interface design concepts interactively with users, with iterative design changes to discover what works best (Gould and Lewis, 1983). But prototyping is no substitute for careful design. Prototyping will allow rapid change in a proposed interface; however, unless the initial design is reasonably good, prototyping may not produce a usable final design. Considering the system development process overall, guidelines application will not necessarily save work in user interface design, and in fact may entail extra work, at least in the initial stage of establishing design rules. But guidelines application should help produce a better user interface. Because guidelines are based on what is known about good design, the resulting user interface is more likely to be usable. Certainly the common application of design rules by all designers working on a system should result in more consistent user interface design. And the single objective on which experts agree is design consistency. </span></text>
</content>
<content>
<layer>card</layer>
<id>16</id>
<text><span class="style31">NTRODUCTION </span><span class="style25">In designing computer-based information systems, special attention must be given to software supporting the user interface. For the past several years, guidelines for designing user interface software have been compiled as a continuing effort sponsored by the Air Force Electronic Systems Division (ESD). Five previous ESD reports have dealt with this subject (Smith, 1980; 1981a; 1982b; Smith and Aucella, 1983a; Smith and Mosier, 1984a). This present report revises and expands previously published material, and proposes a comprehensive set of guidelines for design of user interface software in computer-based information systems. Although a great many changes have been made, much of the text and guidelines material in this report will seem familiar to the readers of previous reports. Different people will read this report for different reasons -- teachers and students, human factors practitioners and researchers, system analysts and software designers, and their managers. Each reader will bring to the task a unique background of experience and interests. Thus some introductory comments are needed to help familiarize readers with the general problems of user interface design and the particular need for guidelines to design user interface software. For the skeptical reader, this introduction offers arguments in favor of guidelines for user interface software design. For the enthusiast who may imagine that guidelines can solve all design problems, this introduction will note some of their limitations. For those readers who wish to apply design guidelines, this introduction describes how the report is formatted, how the guidelines are presented and annotated, and concludes with some recommendations for how the guidelines should be used. </span></text>
</content>
<content>
<layer>card</layer>
<id>17</id>
<text><span class="style31">CKNOWLEDGMENT </span><span class="style25">This report was prepared by The MITRE Corporation. The work reported here was sponsored by the Directorate of Computer Systems Engineering, Deputy for Acquisition Logistics and Technical Operations of the Electronic Systems Division (ESD) of the United States Air Force Systems Command, Hanscom Air Force Base, MA 01731. Continuing funding for this work was provided by the Air Force Computer Resource Management Technology Program, Program Element 64740F, under ESD/MITRE Project 5220. Final publication of these guidelines was funded under Project 5720. The Computer Resource Management Technology Program supports development and transition into active use of tools and techniques needed to cope with the explosive growth in Air Force systems that use computer resources. The objectives of that Program are: ΓÇó to provide for the transition to Air Force systems of computer system developments in laboratories, industry, and academia; ΓÇó to develop and apply software acquisition management techniques to reduce life cycle costs; ΓÇó to provide improved software design tools; ΓÇó to address problems associated with computer security; ΓÇó to develop advanced software engineering tools, techniques, and systems; ΓÇó to support the implementation of high-order programming languages, e.g., Ada; ΓÇó to improve human engineering of computer systems; and ΓÇó to develop and apply computer simulation techniques in support of system acquisition. </span></text>
</content>
<content>
<layer>card</layer>
<id>18</id>
<text><span class="style31">XECUTIVE SUMMARY </span><span class="style25">This report offers guidelines for design of user interface software in six functional areas: data entry, data display, sequence control, user guidance, data transmission, and data protection. This report revises and extends previous compilations of design guidelines (cf. Smith and Mosier, 1984a). If you are a teacher, a student, a human factors practitioner or researcher, these guidelines can serve as a starting point for the development and application of expert knowledge. But that is not the primary objective of this compilation. The guidelines are proposed here as a potential tool for designers of user interface software. If you are a system analyst, you can review these guidelines to establish design requirements. If you are a software designer, you can consult these guidelines to derive the specific design rules appropriate for your particular system application. That translation from general guidelines to specific rules will help focus attention on critical user interface design questions early in the design process. If you are a manager responsible for user interface software design, you may find in these guidelines a means to make the design process more efficient. Guidelines can help establish rules for coordinating individual design contributions, can help to make design decisions just once rather than leaving them to be made over and over again by individual designers, can help to define detailed design requirements and to evaluate user interface software in comparison with those requirements. The design of user interface software will often involve a considerable investment of time and effort. Design guidelines can help ensure the value of that investment. </span></text>
</content>
<name>Introduction…</name>
<script></script>
</card>
card_4980.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style1">here are a number of ways to use these Guidelines effectively. These include: ΓÇó Browsing ΓÇó Searching ΓÇó Gathering</span><span class="style34">ΓêåΓêå Browsing the Guidelines</span><span class="style1">The Guidelines consist of six sections plus an Intrduction. To find out more on the report and the way the Guidelines are organized, go to the Introduction section.Each section (Data Entry, Data Display, Sequence Control, User Guidance, Data Transmission, and Data Protection) is broken down into smaller parts. Clicking on any of these parts will display the appropraite Guidelines for that section. Some Parts have a '</span><span class="style23">t</span><span class="style1">' next to its name, this is a popup menu and further subdivides the guidelines parts. You can click on any guidelines and the data for that guidline will be displayed in a new window.You can use the left and right buttons to navigate as well as the 'Back' button to return to the Guidelines list.To see any references mentioned in the Guidelines, click on the Reference button. This will display a smaller list of references. Click on any reference and another window will appear with the details of that reference. Again, you can use the left and right buttons to navigate as well as the 'Back' button to return to the Guideline.To see any "See Also" Guidelines, click on the See Also button. Click on any of the listed Guidelines to view them.If the References or See Also buttons are in italic font, then there are no References or See Also's for that Guideline.</span><span class="style34">ΓêåΓêå Searching the Guidelines</span><span class="style1">On the Search screen, you can enter keywords and a list of Guidelines with that keyword will be displayed. Clicking on any Guidelines in the list will display the data.</span><span class="style34">ΓêåΓêå Gathering the Guidelines</span><span class="style1">At any stage during your browse, you can click on the Gather Guideline button and it will be recorded in the "gathered" list.Once you have gathered all your guidelines, you can process them by clicking on the "Gather" button from the main screen. You will see a list of the gathered guidelines, which you can view by simply clicking on it name.If you wish to gather the "See Also" guidelines, then make sure this check-box is on (before you gather any guidelines).The Sort button will sort the guidelines into numerical order.The Unique button will remove any duplicate guidelines.The Clear All button will remove all guidelines.The Delete button will display the list of guidelines. You can select (including multiple selections) any guidelines to be removed.The Export button will generate a report including all the text of the Guidelines. You have the option of creating a Text or an WordΓäó compatible document. If you wish any References to be included in the report, then make sure the "Include References in Export" check-box is on.</span></text>
</content>
<name>Help…</name>
<script></script>
</card>
card_3025.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<text><span class="style30">RUIT∆SAM™ Version 1.0</span><span class="style29">.1</span><span class="style1">Written By Renato Iannella (</span><span class="style24">ren@bu.oz.au</span><span class="style1">)Bond Research into User Interface TechnologiesSchool of Information & Computing SciencesBond University, Gold Coast, QLD, 4229, AUSTRALIAText Source: </span><span class="style29">Guidelines for Designing User Interface Software</span><span class="style1"> Smith, Sidney L., & Mosier, Jane. N. MITRE Corporation, Bedford, MA 01730, USA Prepared for Deputy Commander for Development Plans and Support Systems, Electronic Systems Division, AFSC, United States Air Force, Hanscom Air Force Base, Massachusetts, USA Report: ESD-TR-86-278 MTR-10090 August 1986The text from the above report was generated from NaviText™ SAM by Northern Light Software Corporation 24A Pilgrim Drive, PO Box 1599 Westford, MA 01886 USA.Bond University has no affiliation with MITRE Corporation or Northern Lights Corporation.BRUIT∆SAM is in the Public DomainIf you wish to register your copy (and recieve notifications of updates) send an email message to </span><span class="style24">bruitsam@sea.sics.bu.oz.au</span><span class="style1"> with your current version number. Please also send in bug reports and enhancement suggestions.</span><span class="style29">BRUIT∆SAM © Bond University 1991</span><span class="style1"></span><span class="style35">Version Change History</span><span class="style1">V 1.0 01-Dec-91 — First ReleaseV 1.0.1 09-Dec-91 — Added Quit button — Set the guidelines card size window to 512x320 (on 9" monitors, Hypercard will make it smaller ?) — Added ReturnInField detection for Search Words — Checked Search Words are greater than 1 Char</span></text>
</content>
<name>About…</name>
<script></script>
</card>
card_4217.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" >
<script>on mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>17</id>
<type>field</type>
<visible> <false /> </visible>
<dontWrap> <false /> </dontWrap>
<dontSearch> <false /> </dontSearch>
<sharedText> <false /> </sharedText>
<fixedLineHeight> <false /> </fixedLineHeight>
<autoTab> <false /> </autoTab>
<lockText> <false /> </lockText>
<rect>
<left>184</left>
<top>89</top>
<right>387</right>
<bottom>205</bottom>
</rect>
<style>scrolling</style>
<autoSelect> <false /> </autoSelect>
<showLines> <false /> </showLines>
<wideMargins> <false /> </wideMargins>
<multipleLines> <false /> </multipleLines>
<reservedFamily> 0 </reservedFamily>
<titleWidth>0</titleWidth>
<icon>0</icon>
<textAlign>left</textAlign>
<font>Geneva</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<textHeight>16</textHeight>
<name>hash</name>
<script></script>
</part>
<part>
<id>19</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>335</left>
<top>93</top>
<right>436</right>
<bottom>144</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>18607</icon>
<textAlign>center</textAlign>
<font>Courier</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Data Transmission</name>
<script>on mouseWithinset the icon of me to "Phone2"set the icon of me to "Phone3"set the icon of me to "Phone4"set the icon of me to "Phone1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>20</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>341</left>
<top>147</top>
<right>442</right>
<bottom>198</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>6560</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Data Protection</name>
<script>on mouseWithinset the icon of me to "key2"set the icon of me to "key3"set the icon of me to "key1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>21</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>236</left>
<top>147</top>
<right>337</right>
<bottom>198</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>21437</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>User Guidance</name>
<script>on mouseWithinset the icon of me to "Face2"set the icon of me to "Face3"set the icon of me to "Face4"set the icon of me to "Face1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>22</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>229</left>
<top>93</top>
<right>330</right>
<bottom>144</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>10183</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Sequence Control</name>
<script>on mouseWithinset the icon of me to "sequence2"set the icon of me to "sequence3"set the icon of me to "sequence1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>24</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>130</left>
<top>147</top>
<right>231</right>
<bottom>198</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>29589</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Data Display</name>
<script>on mouseWithinset the icon of me to "Display2"set the icon of me to "Display3"set the icon of me to "Display4"set the icon of me to "Display1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>25</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>123</left>
<top>93</top>
<right>224</right>
<bottom>144</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <false /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>17214</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Data Entry</name>
<script>on mouseWithinset the icon of me to "Press2"set the icon of me to "Press3"set the icon of me to "Press4"set the icon of me to "Press1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>26</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>456</left>
<top>105</top>
<right>507</right>
<bottom>153</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>6544</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Gather…</name>
<script>on mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>27</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>455</left>
<top>4</top>
<right>506</right>
<bottom>52</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>26993</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>About…</name>
<script>on mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>28</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>456</left>
<top>156</top>
<right>507</right>
<bottom>204</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>28654</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Search…</name>
<script>on mouseUppush cardgo card (the short name of me)end mouseUp</script>
</part>
<part>
<id>29</id>
<type>button</type>
<visible> <true /> </visible>
<reserved5> 0 </reserved5>
<reserved4> 0 </reserved4>
<reserved3> 0 </reserved3>
<reserved2> 0 </reserved2>
<reserved1> 0 </reserved1>
<enabled> <true /> </enabled>
<rect>
<left>17</left>
<top>129</top>
<right>118</right>
<bottom>180</bottom>
</rect>
<style>shadow</style>
<showName> <true /> </showName>
<highlight> <false /> </highlight>
<autoHighlight> <true /> </autoHighlight>
<sharedHighlight> <true /> </sharedHighlight>
<family>0</family>
<titleWidth>0</titleWidth>
<icon>5</icon>
<textAlign>center</textAlign>
<font>Chicago</font>
<textSize>12</textSize>
<textStyle>plain</textStyle>
<name>Introduction…</name>
<script>on mouseWithinset the icon of me to "Intro2"set the icon of me to "Intro3"set the icon of me to "Intro4"set the icon of me to "Intro1"end mouseWithinon mouseUppush cardgo card (the short name of me)end mouseUp</script>